Re: Error checking ON
[email protected] (Jim Giner)
| Newsgroups | php.general |
|---|---|
| Message-ID | <[email protected]> |
On 7/17/2013 11:49 AM, Tedd Sperling wrote: > Hi gang: > > Considering: > > On Jul 17, 2013, at 11:41 AM, Jim Giner <[email protected]> wrote: > >> Since you state that you haven't made any changes to the system (in general), I'm going to guess that you modified an 'included' file and it has an error in it, such as an unmatched curly brace. As Dan said, turn on all error checking and reporting and see what message you get. > > This is what I do for error checking: > > ini_set('error_reporting', E_ALL | E_STRICT); > ini_set('display_errors', 'On'); > ini_set('log_errors', 'On'); > ini_set('error_log', 'error_log'); > > Is this: > > 1. Sufficient? > > 2. An overkill? > > 3. OK? > > 4. OR, better served with this (and provide an example). > > Cheers, > > tedd > > _____________________ > [email protected] > http://sperling.com > When I'm in development mode, I leave out the last two settings and take my error messages from the screen. Simpler, quicker. I use an include file that is based upon a switch. When it's on, I set my devl settings, when not, I set my prod settings.