Re: 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 13:34 -0400, Daniel Brown wrote:
> On Sat, Aug 2, 2008 at 12:52 PM, Al <news@xxxxxxxxxxxxx> wrote:
> > Here' the snippet I use on all my code files. Default is create and add to
> > error log file on the current dir.
> >
> > I generally echo $error_reporting to remind myself that the error reporting
> > is active.
> >
> > if(true) // TRUE for debug only
> >    {
> >        ini_set("display_errors", "on"); //use off if users will see them
> >    error_reporting(E_ALL);
> >
> >    $error_reporting = '<span style="color:red">Error display and logging
> > on</span>  ';
> > }
> 
>     Quit top-posting, Al, or we'll feed you to the sheep.  ;-P
> 
>     I do a similar thing, but with on-the-fly error display for
> debugging.  Using sessions, only those with a developer flag see any
> errors.  The rest are handled in logs (and yes, using E_ALL).
> 
>     One of my systems uses ~E_CUMMINGS though, because it reports
> things too violently.

Hmmpf!


-- 
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