[ciapug] Error handling

Jerry Heiselman jweida at gmail.com
Wed Dec 28 22:00:35 CST 2005


What you should probably do is leave display_errors = off and at the
top of your application do a ini_set('display_errors', 1);

That way when you are done developing, you just have to comment out
that line to restore it to "production" mode.

As for when you change the value in php.ini, double-check to make sure
the php.ini you are editing is the one being used by PHP.

If that doesn't do it, then the only other time I saw this behavior
was after a bad build on a Solaris box.

Jerry


On 12/28/05, Dave J. Hala Jr. <dave at 58ghz.net> wrote:
> I'm doing some work on a Centos 4.2 box with all the latest patches.
> I'm running php 4.3.9-3.9 and mysql 4.1.12-3.RHEL4.1
>
> In this version by default PHP doesn't send errors to the browser. It
> logs them to a file. This really sucks when you're doing development.
>
> I've tweaked the php.ini so that display_errors = On, and restarted
> apache. This doesn't change anything. I've googled it and this seems to
> be the procedure. It just doesn't work.
>
> Anyone got any thoughts?
>
> :) Dave
>
> --
>
> Open Source Information Systems, Inc. (OSIS)
> Dave J. Hala Jr., President <dave at osis.us>
> 641.485.1606
>
> _______________________________________________
> ciapug mailing list
> ciapug at cialug.org
> http://cialug.org/mailman/listinfo/ciapug
>


More information about the ciapug mailing list