Re: Re: Exposing PHP/errors on production vs. dev

On 8/2/08, Al <news@ridersite.org> wrote: > Here' the snippet I use on all my code files. Default is create and add to > error log file on the current dir. The problem is if the script is fubar, it won't read the error_log ini override... Open question for all: Even though I have error_reporting set to on, and display_errors set to on, sometimes errors occur and it just shows a blank page. Why is that? I used to always get -some- output, now I get nothing. It's quite annoying. I am excited for PHP 5.3's ini settings features - then I can create a PHP error log per each docroot (manually, for now), or I suppose if I can remember the syntax in php-fpm I can already do that. Problem is then I just need to configure things to rotate/reset those logs every so often. (heads up: feature request, error_log_max_filesize!)