Req #54537 [Opn->Csd]: production value for html_errors should be On

Edit report at https://bugs.php.net/bug.php?id=54537&edit=1 ID: 54537 Updated by: tyrael@php.net Reported by: tyra3l at gmail dot com Summary: production value for html_errors should be On -Status: Open +Status: Closed Type: Feature/Change Request Package: *Configuration Issues PHP Version: 5.3.6 -Assigned To: +Assigned To: tyrael Block user comment: N Private report: N New Comment: This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. For Windows: http://windows.php.net/snapshots/ Thank you for the report, and for helping us make PHP better. fixed in 5.4: https://wiki.php.net/rfc/error-formatting-for-developers http://svn.php.net/viewvc?view=revision&revision=314761 Previous Comments: ------------------------------------------------------------------------ [2011-04-15 22:31:33] tyra3l at gmail dot com probably you know, but you can re-enable html_errors for cli via ini_set: http://www.php.net/manual/en/features.commandline.differences.php for example: php -d display_errors=1 -d error_reporting=-1 -r 'ini_set("html_errors", 1);trigger_error("foo", E_USER_NOTICE);' Tyrael ------------------------------------------------------------------------ [2011-04-15 22:16:21] tyra3l at gmail dot com sorry, I can't follow you. "Is a dynamic plain text web page that hard to imagine?" no, but the majority of the php sites out there use html as the primary output type. you can turn off the html_errors if you are dealing with plain text files. "I know the CLI SAPI has html_errors = 0 hard coded in but why force people to turn off an option that provides little to no benefit..." so only the apache SAPI would be affected, where the majority of the users use html output. but I think that this option should affect anything in a production system, because you turn off the error_reporting in production (and PHP also suggests that, so any distribution which follows the suggestions of the php.ini-* files wouldn't be affected by this change. at all) and both error_reporting and html_errors is enabled in the php.ini-development, so for the text/plain people that would be a problem also. Tyrael ------------------------------------------------------------------------ [2011-04-15 21:47:55] dtajchreber@php.net Is a dynamic plain text web page that hard to imagine? What about non browser output? I know the CLI SAPI has html_errors = 0 hard coded in but why force people to turn off an option that provides little to no benefit... ------------------------------------------------------------------------ [2011-04-15 17:04:24] derick@php.net I agree. There is no reason why html_errors should be off in any case. Especially because the reasoning is non-sense. ------------------------------------------------------------------------ [2011-04-15 12:18:12] tyra3l at gmail dot com Description: ------------ I've noticed, that we suggest setting the html_errors in production to Off, which is an odd thing: in production one should display errors, but if he does, then I can't see why would be more appropriate not to use html errors. could you elaborate on this please? ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=54537&edit=1