Debugging

tripwater

Well it took some time but we figured out how to set the error handling in the ini file to E_ALL, E_ERROR, E_WARNING etc.

We had everything setup and working then we had to restart the server and it for some reason, reset the ini file back to the way it was. SO we went back to the ini file and set it back up but now it does not work.

We even set it to just E_ALL. And nothing. We just get a white page.

Any ideas? We were trying to just use E_PARSE (parse errors), E_ERROR (fatal errors), E_WARNING (warnings)

like so:

E_PARSE | E_ERROR | E_WARNING

Like I said it worked in the beginning. But now even just having E_ALL is not working. Tell me we don't have to reboot the server for this to work...we have restarted the server a few times now and it is not working. The file is not getting reset when we make the changes in cpanel so lesson learned.

thank you for any help with this.

cybercrypt13

I work with Tripwater, wanted to add that we've also tried to use the error_reporting(E_ALL); function inside our files. I thought it was going to work as I created an error in one file and it properly showed the error. However, I went into another file and caused an error by doing the same thing I did in our function page and nothing. Back to a blank page.

Its at least working some of the time but still not working.

We've turned on Show Errors in php.ini file and also made changes through Cpanel instead of to the file directly to prevent things from getting reset again.

Any help would be appreciated as we're pretty much dead until we can get errors to show up.

Thanks,

laserlight

You might want to seek your hosting provider's help. In the mean time, you could continue development work by installing PHP and other necessary tools on your local computers.

Roger_Ramjet

So, it's your own server since you are able to reboot it.

The reason things get reset when you are forced to reboot would probably be because NIX will revert to 'last known good' configuration when a reboot is forced. What you need to do after editing config/ini files is to do sync to force write the file to disk (NIX uses lazy write). I personally would then do a shutdown and boot to make the new configuration the 'last known good'.

PS you should always run sync before shutdown.