No output when cache is unreadable

[mopatop]

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.

See ​http://docs.python.org/tut/node10.html#SECTION0010300000000000000000

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!

[davidhouse]

I can't replicate this. Anyone else? I gave my cache dir r-x------ permissions and my WP installation continued to function.

[davidhouse]

Closing due to lack of feedback. I did ask in #wordpress and skippy couldn't replicate this either. May be a suexec-related bug, reopen if evidence is found to support that.

[ryan]

Try it with safe_mode turned on. safe_mode is screwy. I just added a check in the cache to turn off cache persistence if safe_mode is on instead of trying to work around the damn thing. :-)

[3436]