No output when cache is unreadable
|Reported by:||mopatop||Owned by:|
I recently configured suexec on one of our servers and every single Wordpress 2 blog mysteriously stopped displaying output. The problem was WP couldn't read wp-content/cache. Eventually I grepped the source for every die/exit/quit until I found out where it was exiting, which took a long time.
I realise this is a hard problem to fix, I recommend displaying a message when WP is unable to read the cache, which would help system administrators a great deal.
My fix was:
# updatedb; rm -r `locate wp-content/cache`;
As a side note, this problem was caused because you prolificly supress errors. If you're running functions like header() and you don't care if they do or do not succeed, you're probably doing something wrong. Suppressing errors masks real programming errors, as above.
The last except clause may omit the exception name(s), to serve as a wildcard. Use this with extreme caution, since it is easy to mask a real programming error in this way!