[TYPO3-core] RFC #10228: Feature: displayErrors=2, but still display errors on CLI

[Ernesto Baschny [cron IT]]

This is an SVN patch request.

Type: Feature

Bugtracker reference:
http://bugs.typo3.org/view.php?id=10228

Branches: trunk

Problem:
Many sites set displayErrors=2 and have devIPmask to a list of IPs from
the developer. This won't disturb the public, but the developer gets PHP
errors, which is nice.

Unfortunately this also disables PHP errors from being outputted when
running CLI scripts (as there is no IP adress to check). This is
particularly important if I set some cronjob running a CLI which can
"break".

So suggested is a new setting displayErrorsForceOnCLI (boolean) which
will enable error output on CLI, even if displayErrors=2.


Solution:
See attached patch.

An alternative way would be to handle the CLI as "127.0.0.1" (or special
word "cli" in devIPmask), so that no new setting is required, just add
"127.0.0.1" (or "cli") to the devIPmask, and make that also apply to
other areas where the CLI doesn't output anything, e.g. the calls to
"debug()"). Comments?


Cheers,
Ernesto
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug-10228-displayErrorsCLI.diff
Type: text/x-diff
Size: 3057 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090122/f9df4d44/attachment.diff