I had to delete from my blog as well, it did horrible things to it. Slowed it to a crawl, created errors etc.

Thanks for the tips Simon.

I did test the plugin on a non-vital domain first, but failed to notice the plugin was not recently updated.

I would have been extremely wary about installing a plugin that hasn’t been updated since September 2007! WordPress has changed a hell of a lot since then…

When I’m investigating a new plugin (especially one that is providing absolutely critical functionality), I always check how recently the plugin was updated, how active the author is, I check out comments & answers on the support forum, etc.

I then search for a key phrase (e.g. “cache”) on wordpress.org/extend/plugins – you see below each result the date the plugin was updated, number of downloads and user ratings – all very helpful stuff.

Turns out the incident that night was a ddos.

Can’t say I know for sure what happened with wp-cache, why it didn’t work for me. But I have one theory–maybe wp-cache broke because of the ddos, maybe it cached blank pages? Anyway, I don’t plan to investigate wp-cache further, but figured it was worth mentioning.

Update: turns out my host had an “incident” that night, most likely unrelated to the wp-cache plugin. However, my non-cached sites were definitely working while the cached site was not working.

I suppose it’s possible the downtime caused wp-cache to break. Maybe blank pages were cached? But there are other reasons to not use wp-cache: the author says on his site he wants someone else to take over development of it. Sounds like he doesn’t have time for it.

In any case, I’m going to try Super Cache ASAP.

I just realized you’re the author of it. Now I feel dumb.

Thanks for the comment Donncha. Yes, I’m going to try installing it today.

Are you using Super Cache? How do you like it?

Why not just use WP Super Cache? Much better and faster than any other caching plugin. :)