Forum Moderators: phranque

Message Too Old, No Replies

E ALL breaks php 5.2.6

when turned on in php.ini

         

henry0

10:41 pm on Jul 1, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If I turn error reporting E_ALL on
on my dedicated server
then php5.2.6 will break
what seems to be the problem?
thanks

eelixduppy

4:55 am on Jul 2, 2008 (gmt 0)



Is your syntax correct? Can't seem to think of anything other than improper syntax in your php.ini. Check to see if you are correct. It should look like the following:

error_reporting = E_ALL

henry0

11:28 am on Jul 2, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Thanks eelix,
my answer is kind of strange:
Yes and Not :)

the server is located where WebmasterWorld used to be
they obviously have some strange very own setup

I have been there for years, on a few of my sites
that are not yet php5.2.6 (I'm updating)
php.ini worked with purely getting rid of " ; " and leaving E_ALL un commented.
but it seems that the correct full syntax does apply
starting php5.2.2 or 2.1
I will try the full syntax and report
further my office test beds are both running with the short syntax only using E_ALL
that I'll like to know the reason for?

eelixduppy

9:09 pm on Jul 2, 2008 (gmt 0)



What short syntax are you referring to?

henry0

9:36 pm on Jul 2, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



simply
E_ALL

eelixduppy

9:45 pm on Jul 2, 2008 (gmt 0)



I'm pretty sure this syntax isn't suppose to work. This brings up the question: Were you editing the correct php.ini file in the first place? Sometimes you can edit the configuration file and it will be the wrong one; I know I have done that before.

I would try to use the actual syntax and see if that fixes your problem.

As far as it working on your other servers, see if you were changing the correct php.ini file, and make sure you are restarting your server each time.

[edited by: eelixduppy at 10:13 pm (utc) on July 2, 2008]

henry0

10:08 pm on Jul 2, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I know the dreal :)
I went up to forcing an error in the php.ini to be sure I was editing the correct one!
and yes it still works in that state in a site that was not updated.
Anyway I fixed it by not allowing any error reporting via php.ini and gettting the error via .htaccess
next best thing is to allow for error loging and read the log