On Sun, 24 Jun 2012, Daniel Llewellyn wrote:
In the wordpress community this problem is known as a WSOD or White
Screen Of Death.
In my experience it is usually caused by wordpress requesting a
function which hasn't been installed or enabled, such as if you
haven't got the mysql module (php5-mysql in debian). Different
wordpress plugins also come with their own requirements and will also
cause this WSOD failure when the relevant modules aren't available.
Remember that in at least debian-based systems there are different
php.ini locations for cli, cgi, fpm and apache2 SAPIs, so having a
successful execution in php-cli may not be indicative that it will
work correctly when running through php-cgi (the sapi that suphp
interfaces).
Generally, when WP calls a bad function it logs to the error log, which in
this case it did not.
And I was testing it from the command line with /usr/local/bin/php-cgi,
which worked, although the previous comment about not duplicating the
calling environment exactly does apply.
-Dan
--
"Check it out, it's just like Christmas. Except it sucks."
-Jason Seguerra, 3/2/05
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
Site: http://www.gushi.org
---------------------------
_______________________________________________
suPHP mailing list
[email protected]
https://lists.marsching.com/mailman/listinfo/suphp
