Digg This has been covered several times already, but I thought it was worth mentioning again since a number of popular Digg posts have been afflicted with the curse of the “Digg effect” recently.

There’s nothing more frustrating than seeing your server throw a 403 forbidden error right when you hit the front page (as its not the ideal way to greet your tens of thousands of new visitors).

Assuming your host is not completelty useless, there’s a very easy fix for this: install the wp-cache plugin. Be sure to get version 2 of the wp-cache plugin. I’ve had 1.0 give me problems on the latest WordPress versions, so go with 2.0 (especially if your installation is newish). Unzip it to your plugins folder and activate it.

Make sure it’s enabled under options > wp-cache.

To be sure it’s working, go to any page on your site, refresh it, and view the page’s source code. At the bottom you should see something like this:


-- Dynamic Page Served (once) in 0.477 seconds --
-- Cached page served by WP-Cache --

If you do, the caching page is working properly. In my experience sometimes you have to disable and re-enable the plugin to make sure it’s working right. Also, sometimes there’s a delay in when it starts caching. Thirdly, keep in mind that your browser might be caching the page as well, so restart your Firefox or IE-explorer to be sure.

Now next time you write a good post, just make sure your wp-cache plugin is working.

If you’re curious why this makes such a big difference, here’s the quick (and possibly slightly innacurate) lowdown on what this plugin does: it caches a version of each page (takes a snapshot and stores it as a static file) and serves that one to visitors so every new visitor does not make your wordpress run a bunch of mysql database queries. If you don’t cache and get 12 visitors per second (coming from Digg, Reddit, etc.) your server and database will get overwhelmed and crash.