>
Cc: <>
Sent: Monday, January 19, 2004 2:53 PM
Subject: Re: [PHP] Error Reporting help
> Chris Edwards wrote:
> > but do I need to do something to
> > get PHP to actually work off of these setting once they have been
changed,
>
> Restart your web server.
>
>
On Tuesday 20 January 2004 03:44, Chris Edwards wrote:
> Here's a snippet from my PHI_INI
>
> ; - Show all errors
> ;
> error_reporting = E_ALL
> ;error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING & ~E_CORE_WARNING &
> ~E_USER_WARNING & ~E_USER_NOTICE & ~E_COMPILE_WARNING
>
> display_errors =
Chris Edwards wrote:
but do I need to do something to
get PHP to actually work off of these setting once they have been changed,
Restart your web server.
--
---John Holmes...
Amazon Wishlist: www.amazon.com/o/registry/3BEXC84AB3A5E/
php|architect: The Magazine for PHP Professionals – www.phparch.
Here's a snippet from my PHI_INI
; - Show all errors
;
error_reporting = E_ALL
;error_reporting = E_ALL & ~E_NOTICE & ~E_WARNING & ~E_CORE_WARNING &
~E_USER_WARNING & ~E_USER_NOTICE & ~E_COMPILE_WARNING
display_errors = On
The commented out error_reporting was the original setting and
"dis
On Monday 19 January 2004 22:34, Chris Edwards wrote:
> I retried most of the combinations and still cannot get it to report syntax
> errors. If I have errors, from say undefined variables, the error handler
> catches those just fine.
Again:
> > But if "display_errors" (in php.ini) is disabled t
Thanks for all you replies, most of what you have suggested, I had already
tried, in vain, before joining the list.
I retried most of the combinations and still cannot get it to report syntax
errors. If I have errors, from say undefined variables, the error handler
catches those just fine.
Questi
On Monday 19 January 2004 07:30, Chris Edwards wrote:
> It's almost like it parses it before it tries to execute any lines and if a
> syntax error occurs, it doesn't execute any of the script.
That's right.
> The prior version would run up until the syntax error and then give you the
> line if e
Tried that, thanks, no joy.
It's almost like it parses it before it tries to execute any lines and if a
syntax error occurs, it doesn't execute any of the script.
The prior version would run up until the syntax error and then give you the
line if error, which usually meant the syntax error was on
Chris Edwards wrote:
My hosting company recently upgraded to PHP 4.3.0. Since doing this I no
longer get syntax type errors, from my typo's inside my PHP scripts. These
use to come up in my browser when that page was requested and the script
run.
You probably need to have them turn on display_error
Chris Edwards wrote:
[cut]
> For example if I code
>
> echo "This is a syntax error because of the double quote start and the
> single quote end ';
>
> I just get a blank screen.
>
> I have 14 pages of PHP settings printed out, so for any kind person that can
> help, I can respond wit
My hosting company recently upgraded to PHP 4.3.0. Since doing this I no
longer get syntax type errors, from my typo's inside my PHP scripts. These
use to come up in my browser when that page was requested and the script
run.
I have spent hours going through the online help, trying to set a number
11 matches
Mail list logo
