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

Ernesto Baschny [cron IT] ernst at cron-it.de
Fri Jan 23 10:27:39 CET 2009


Martin Kutschker wrote: on 23.01.2009 09:18:

>> 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.
> 
> Make it a command line-switch of cli_dispatcher.php. Perhaps even with
> the option to install an error handler that collects all messages and
> prints the errors at the end of the script.
> 
> BTW, I'm surprised you want PHP warnings/errors scattered in your script
> output.

Well, I would have needed that once (cronjob that failed after some
unrelated changes because of some PHP error) to get informed that the
cronjob ceased working.

I will think of something else and so withdraw this RFC for the time being.

Cheers,
Ernesto


More information about the TYPO3-team-core mailing list