Bug #83317
closed
Syslog - Core errors are logged without setting column error
0%
Description
with TYPO3 v9.0.0 i see errors in log without setting the column error (it's still "0")
Example:
Core: Error handler (BE): TYPO3 Deprecation Notice: Second argument $deepDirectory of GeneralUtility::mkdir_deep() will be removed in TYPO3 v10.0, use a combined string as first argument instead. in /Users/steffen/Development/web/libs/typo3/typo3_src-9.0.0/typo3/sysext/core/Classes/Utility/GeneralUtility.php line 2056
As this comes from Core Error Handler, even it's only a Notice, i think error column should be set. I use a cleanup where i delete all entries where error > 0, and those entries are shown in log as errors.
Updated by
Updated by Steffen Kamper almost 7 years ago
will try to find the time between the days
Updated by Steffen Kamper almost 7 years ago
The problem is in TYPO3\CMS\Core\Error\ErrorHandler->handleError
switch ($errorLevel) is insufficient, as the errorLevel is a number containing several flags. So this switch should be changed to match containing flags.
Setting severity by default to "0" is Imho wrong for this function, minimum severity should be 1.
Updated by Markus Klein over 4 years ago
- Status changed from New to Needs Feedback
Reading this report again some long time later, I currently fail to understand the problem.
Would you mind elaborating on the problem again? Thanks a lot.
Updated by Benni Mack over 4 years ago
- Status changed from Needs Feedback to Closed