[TYPO3-core] RFC #12516: The error handling is too verbose
Rupert Germann
rupi at gmx.li
Mon Nov 9 14:38:45 CET 2009
Hi,
this is a SVN patch request.
Type: improvement of existing features
Bugtracker references:
http://bugs.typo3.org/view.php?id=12516
Branches: Trunk
Problem:
each PHP error/warning/notice which is handled by the error handling
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.
Reminder for me: documentation needs to be updated
greets
rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 12516.diff
Type: text/x-diff
Size: 2891 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20091109/a5321a1e/attachment.diff>
More information about the TYPO3-team-core
mailing list