Actions
Feature #19889
closeddisplayErrors=2 and no errors on CLI
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-01-22
Due date:
% Done:
0%
Estimated time:
PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:
Description
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. 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.
(issue imported from #M10228)
Actions