Project

General

Profile

Actions

Bug #21503

closed

Give admins the possibility to configure which errors should be logged to which log

Added by Rupert Germann about 15 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2009-11-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Problem:
each PHP error/waring/notice which is handled by the errorhandling produces a log entry in the sys_log table (ext:belog) and also in the configured syslogs. This is good for debugging but might not be a wanted behaviour on production sites with old extensions installed.

Solution:
Add 2 new typo3_conf_vars for configuring which errors should be logged to each log:

$TYPO3_CONF_VARS['SYS']['syslogErrorReporting'] = E_ALL ^ E_NOTICE
Configures which PHP errors should be logged to the configured syslogs (see: [SYS][systemLog]). If set to "0" no PHP errors are logged to the syslog. Default is "E_ALL ^ E_NOTICE" (6135).

$TYPO3_CONF_VARS['SYS']['belogErrorReporting'] = E_ALL ^ E_NOTICE
Configures which PHP errors should be logged to the "syslog" table (extension: belog). If set to "0" no PHP errors are logged to the sys_log table. Default is "E_ALL ^ E_NOTICE" (6135).

Note:
Exceptions are still logged to every available log (if an exception handler is registered).
If a devlog extension is installed and $TYPO3_CONF_VARS['SYS']['enable_errorDLOG'] is enabled all error handler errors are logged to the devlog table.

(issue imported from #M12516)


Files

12516.diff (2.82 KB) 12516.diff Administrator Admin, 2009-11-09 14:30
Actions #1

Updated by Rupert Germann about 15 years ago

committed to trunk rev 6471

Actions

Also available in: Atom PDF