WP Super Cache

WP Super Cache is a full page caching plugin for WordPress that makes your website run much faster!

I’ve just released a new version and the biggest change in this one is the addition of Content Delivery Network (CDN) support thanks to Mark Kubacki who allowed me to integrate his OSSDL CDN Off Linker plugin. (Please go visit his blog and say thank you if you use this feature!)

The CDN support simply rewrites images, CSS and Javascript files so they point at a different hostname. That hostname can be another virtual host on your own server (aka “Poor Man’s CDN”) pointing at your WordPress install or a fully fledged CDN. If your CDN supports “origin pull” then all the files on your server will be copied there as they are requested by visitors. Otherwise you’ll have to transfer the files over manually.

Apart from that, bugs have been fixed, a few features have been tweaked including the uninstall script which has been streamlined somewhat.

I also added links (on the “Easy” settngs page) to some plugins and tools you may find useful in making your site run faster.

Problems? Go to the forum and someone may already have had that problem and solved it. If not, post there and you’ll get a reply.

35 thoughts on “WP Super Cache

    1. lol 🙂 looking forward to 1.0.0 🙂

      i like the minify addon / plugin for super cache. finally its working great and reduces html size a little bit. its even working side by side with mod_pagespeed, of course.

      i only think this minify add on should`t strip adsense tags / comments of the code (adsense start.. end) because.. you know what i mean. 😉

      by the way.. my girlfriend orderd the htc desire z yesterday. i`m still on touch hd with custom rom.. waiting for a tegra 2 devide 😀

      i wish you the best & thank you very much donncha.


  1. Great news, more competition for us end users. With the round update release; pls remove the 0. at the beginning and simply show 10.0, then 10.0.1 etc. I am experimenting with CDN and diff. caching plugins at the moment.

    Would be great of someone made a practical article about pluses and minuses for various CDN system providers; who is better for various site sizes/traffic/future considerations for a CDN service. Thank you.

  2. If you chose to move the wp-content directory to a CDN (e.g. CloudFront) using this new feature of WP SuperCache, how do the individual SuperCache cache files get written to the CDN location without the security keys? Or would you simply exclude .html files from the transfer? And beyond the wp-includes directory, what other WordPress directories might be suitable for moving to a CDN with this new feature?

    1. Gary – the cache files don’t get written to the CDN at all. The plugin doesn’t write to the CDN, it just rewrites urls pointing at static files so visitors request the files hosted by the CDN, the CDN then requests them from your site and stores them.
      When your visitors request pages from your site they don’t request /wp-content/cache/supercache/example.com/index.html.gz, they just request the front page.

      You could try wp-admin but I wouldn’t. The only other directories you might try are ones that are specific to your site. Ones with images or Javascript or CSS…

  3. Just updated the plugin and activated successfully for my main site.

    However when I go to the WPSC settings page I’m getting a “Cannot load wpsupercache.”

    Running the latest WP 3.01 with MS enabled. 🙁

      1. I keep searching the cause of this error. So far, I have noticed that:

        – it’s happening on a multi-site and not in a one-site installation

        – calling /wp-admin/options-general.php?page=wpsupercache gaves an error 500 on the server

        I’ll keep posting my findings to see if we can solve this issue.

    1. The problem (in my case) lays in the wp_cache_add_pages() function (in wp-cache.php):

      it calls the add_submenu_page() but not the add_options_page().

      Nevertheless, in plugins.php I see a link to


      that gaves this error 500…


      works though…

      Any thoughts?

  4. Donncha,
    There is some kind of conflict between WP Super Cache Version and Gravity Forms 1.4.5.

    When they are both activated, I get errors in the dashboard feeds – Incoming Links, Plugins and WordPress Blog.

    This is the error:
    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 122880 bytes) in /xxxx/xxxx/xxxx/wp-includes/class-simplepie.php on line 14440

  5. Thank you for the awesome caching plugin. Now i can get a gazillion hits on my pages and it won’t even crash the server.

  6. I encountered a strange problem that could be a supercache problem.

    Whenever I enter a comment for the first time I get directed to domain.com/link.html#comment-

    Then when I submit the second time it works flawlessly. Could this be a caching problem with the comments. Any ideas?

  7. WPMU issue:

    It just took me 30 mins ta figure out that link in the admin head message after instal (WP Super Cache is disabled. Please go to the plugin admin page to enable caching.) goes to the single instal wordpress page and gives an error in wpmu.

    link is: /wp-admin/options-general.php?page=wpsupercache

    should be: /wp-admin/ms-admin.php?page=wpsupercache

    p.s- its in the plugin description area too(by active/deactivate)

  8. hi there!

    Thanks for this. But quick question: ever since I download WP Super Cache whenever I change the coding, it doesn’t register on the webpage at all! It’s as if i’m not changing the coding or something….help! What should I do??



  9. Hi Donncha – is there a way for the static files produced by super-cache to also be served from a cdn?

    We use edgecast for our static images and your plugin and it works nicely.

    I’d love to be able to serve the static cached files from an edge location as well.

    It would then make a website effectively ‘local’ in most countries of the world (that is, where’s there’s a CDN node).

    I think I saw a branch of your plugin which tried to do this. Could you please update me on whether it’s achievable with your plugin?

    thanks, Zac

    1. Zac – I don’t think it’s possible. The url for your pages will change to the CDN url and make the browsing experience on your site awful for users. What you want to do is done via DNS and geoip and is beyond the scope of this plugin unfortunately.

      1. Thanks for your reply Doncha. I suspected as such…

        I hope I can ask one last question, but one of our sites receives about 20,000 comments monthly.

        Am I right in assuming if a user has left a comment, they have a WP cookie set and therefore don’t receive a cached page?

        On that site, commenters make up a high-ish proportion of users.

        For this reason we’re using w3 for the db and object caching it offers, but I’d love your view on how Super cache performs on a high comment site.

        1. Zac – they won’t get a cached page only if you have enabled the “don’t cache for known users” option on the settings page. Otherwise they get a personalised cache page. As I said to Michael, you could use db cache reloaded or memcached to cache MySQL queries too. On a high comment site using the “cache rebuild” function helps a lot. Check out the performance graph on this post. That post explains how it solves the problem of regenerating pages where there is lots of activity.

          1. Thanks Donncha – I might try this and see how it works.

            Great plugin and support.

            Cheers, Zac

  10. ..maybe a stupid thing.. if your blog has over xx.000 Posts saved in the Database would it be better (speed, last) to load some x.000 post from textfile (content of post) and to get rid of these 3-4 year old articles in the database..?

    1. Lazy – you could I suppose, but it’s not convenient and most blogs probably still allow comments on old posts. You could preload all the posts on your blog once, then the next time preload only the newest few thousand posts. Themes and sidebar widgets won’t update however.

Leave a Reply

%d bloggers like this:

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.