Re: Exposing PHP/errors on production vs. dev
| From: | mike | Date: | Sat, 02 Aug 2008 08:18:43 +0000 |
| Subject: | Re: Exposing PHP/errors on production vs. dev | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-277606@lists.php.net to get a copy of this message | ||
On 8/2/08, Richard Heyes <richard.heyes@gmail.com> wrote:
> > Personally, and I know I'm not alone here... I keep E_NOTICE enabled
>
> Then you're both mad. Users really shouldn't see any error regardless,
> so error reporting IMO should be off entirely. A blank screen that you
> can blame on a variety of things is far preferable to users knowing
> that your website is broken. In production I keep error_reporting set
> to 0. There are a variety of things you could also do like log them to
> a file or have them emailed to you so that you get notified when
> errors occur.
That's what we're saying.
He's saying he is LOGGING everything (error_reporting) not
display_errors - where it would output to the user :)
display_errors and maybe display_startup_errors are the key ones afaik
that expose any PHP related errors to the user. that's why I started
this thread to confirm my logic.