Re: Exposing PHP/errors on production vs. dev

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2008-08-02 at 10:32 +0100, Richard Heyes wrote:
> >> 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.

*lol* :)

Cheers,
Rob.
-- 
http://www.interjinn.com
Application and Templating Framework for PHP


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux