Re: Exposing PHP/errors on production vs. dev
| From: | Richard Heyes | Date: | Sat, 02 Aug 2008 09:32:32 +0000 |
| Subject: | Re: Exposing PHP/errors on production vs. dev | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-277607@lists.php.net to get a copy of this message | ||
>> 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 :)
Oopsy. Missed that. Well as long as display errors is off then I guess
there's no problem with error_reporting set to E_ALL, and it would
even be preferable I guess.
--
Richard Heyes
http://www.phpguru.org