[ciapug] Error handling

[Dave J. Hala Jr.]

I really don't want to do this. I hate to be a "grumpy old set in his
ways" kinda guy, but this and the log file is very unproductive on a
development server.  I understand that on a production server its a good
idea.

I'll do some more digging this morning. Its got to be a combination of
config variables that is screwing me up.

On Thu, 2005-12-29 at 06:20, Carl Olsen wrote:
> I have this problem all the time.  I use error_log().  It sends me an email
> message.  I put the page name and the line number, or something to identify
> where it's located, in case I have several of them.  It's kind of klunky,
> but it definitely works.
> 
> -----Original Message-----
> From: ciapug-bounces at cialug.org [mailto:ciapug-bounces at cialug.org] On Behalf
> Of Dave J. Hala Jr.
> Sent: Wednesday, December 28, 2005 9:47 PM
> To: PHP List
> Subject: [ciapug] Error handling
> 
> 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