A user of mine is coming up with an error that manifests as... well... a blank page. What's mysterious about it, however, is the following facts:
- Error reporting is on and set to E_ALL | E_STRICT
- PHP nor Apache do not appear to be segfaulting
- Attempting to pin down the exact location of the error with a die('Error!') is futile
This tricky conundrum has left me scratching my head, and, of course, it's not reproducible. Anyone have any insights into the problem (I'm thinking maybe it's output buffering).
Thread is here: http://htmlpurifier.org/phorum/read.php?3,281
Blank page error
Moderator: General Moderators
- Ambush Commander
- DevNet Master
- Posts: 3698
- Joined: Mon Oct 25, 2004 9:29 pm
- Location: New Jersey, US
-
nickvd
- DevNet Resident
- Posts: 1027
- Joined: Thu Mar 10, 2005 5:27 pm
- Location: Southern Ontario
- Contact:
Run a packet sniffer on the connection... It may not be coming back at all... or alternatively try livehttpheaders to see what is happening.
The latest version of firebug has a 'net' tab, which shows a decent amount of info regarding the various goings-on behind the scenes...
The latest version of firebug has a 'net' tab, which shows a decent amount of info regarding the various goings-on behind the scenes...
Re: Blank page error
Is this set in the php.ini? If it is a parse error error_reporting(E_ALL) is useless.Ambush Commander wrote:- Error reporting is on and set to E_ALL | E_STRICT
Also take a look at http://php.net/ref.errorfunc#ini.display-startup-errors and http://php.net/ref.errorfunc#ini.display-errors