Error checking ON

[Tedd Sperling]

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

_____________________
***@sperling.com
http://sperling.com

[Jim Giner]

Post by Tedd Sperling

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.

ini_set('error_reporting', E_ALL | E_STRICT);
ini_set('display_errors', 'On');
ini_set('log_errors', 'On');
ini_set('error_log', 'error_log');
1. Sufficient?
2. An overkill?
3. OK?
4. OR, better served with this (and provide an example).
Cheers,
tedd
_____________________
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.

[Daniel Brown]

Post by Tedd Sperling

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.

ini_set('error_reporting', E_ALL | E_STRICT);
ini_set('display_errors', 'On');
ini_set('log_errors', 'On');
ini_set('error_log', 'error_log');
1. Sufficient?
2. An overkill?
3. OK?
4. OR, better served with this (and provide an example).

That's standard practice. Sometimes, though, it isn't enough, and
we find ourselves using Derick's Xdebug, mod_top, or performing an
strace on either the execution or attached to a process. For nearly
all cases, though, that's sufficient without being overkill (except
for production cases).

--
</Daniel P. Brown>
Network Infrastructure Manager
http://www.php.net/

[Tedd Sperling]

Post by Daniel Brown

Post by Tedd Sperling
ini_set('error_reporting', E_ALL | E_STRICT);
ini_set('display_errors', 'On');
ini_set('log_errors', 'On');
ini_set('error_log', 'error_log');
1. Sufficient?
2. An overkill?
3. OK?
4. OR, better served with this (and provide an example).

That's standard practice. Sometimes, though, it isn't enough, and
we find ourselves using Derick's Xdebug, mod_top, or performing an
strace on either the execution or attached to a process. For nearly
all cases, though, that's sufficient without being overkill (except
for production cases).

Daniel:

Thanks -- I always wondered about that.

Cheers,

tedd

PS: Of course, turned OFF for production. :-)

_____________________
***@sperling.com
http://sperling.com

[Jim Lucas]

Post by Tedd Sperling

Post by Daniel Brown

Post by Tedd Sperling
ini_set('error_reporting', E_ALL | E_STRICT);
ini_set('display_errors', 'On');
ini_set('log_errors', 'On');
ini_set('error_log', 'error_log');
1. Sufficient?
2. An overkill?
3. OK?
4. OR, better served with this (and provide an example).

That's standard practice. Sometimes, though, it isn't enough, and
we find ourselves using Derick's Xdebug, mod_top, or performing an
strace on either the execution or attached to a process. For nearly
all cases, though, that's sufficient without being overkill (except
for production cases).

Thanks -- I always wondered about that.
Cheers,
tedd
PS: Of course, turned OFF for production. :-)
_____________________
http://sperling.com

But... It won't work in all cases. I find it best to set these
settings in the server itself. Not in code. Sometimes, if you have
broken code that cannot be parsed, your commands listed above will never
be executed. Therefor they will never do any good.