by: DonnchaPosted on:

WP Super Cache 0.6

It’s been a while since the last release of WP Super Cache, so it’s about time to release the updated code on the world!

This plugin allows a WordPress blog to be served directly from static HTML files just like another popular blogging engine.

When this plugin was originally released some users noticed strange folders being created in the root folder of their blogs. I was never able to replicate it and despite my efforts to track down the bug it remained unfixed. Well, I fixed that bug thanks to whooami and to Jennifer who allowed me to login to her server and debug my script. Barry was astute enough to figure out why it happened.

Other changes include:

  • Compressed cache files are deleted properly now, props John Pozadzides.
  • Documentation got a serious update. I added a FAQ, and the Troubleshooting section has been expanded.
  • The .htaccess is not updated until the user clicks a button in the backend now.
  • The listing of cached files is gone for this release as it was inaccurate. It didn’t include super cached files.
  • The backend admin page has been rearranged slightly. Advanced features go at the very end, and if you’re only using the WP Cache functionality, the Super Cache items disappear. The mod_rewrite check and .htaccess items are only enabled if Super Cache is enabled now.
  • Not all blogs have permalinks ending in a slash so I added a slash back into the mod_rewrite rules. If you use .html at the end of your permalinks you’ll appreciate this. props Michael R Aulia for that.

One more thing to note. If your blog is visible at a URL with or without the www you should decide which one is more important to you and download the Enforce www preference plugin. Super cached files are stored in a directory named after the hostname so if you go to the www URL and someone else goes to the url without the www they won’t see the static html file. Deciding on one URL avoids any issues with duplicate content too which is probably much more important too.

Grab WP Super Cache 0.6 from the download page!

35 thoughts on “WP Super Cache 0.6”

  1. Pingback: New Version of WP Super Cache Released - Blog Tipz

  3. DLing. Hopefully this solves my Supercache conflict NexGen Gallery plugin. Everytime I try to run it blocks all of the subpages of my gallery. I have running this plugin with Supercache disabled.

    Fingers crossed. 🙂

    Reply

  5. Thanks for your great work on this Donncha, it’s very helpful for crappy servers!

    I’m thinking that the enforce-WWW thing probably doesn’t matter for people using WP 2.3 or later, since it has canonical urls…

    Reply

  6. Enforce WWW preference is built-in to WordPress 2.3 or higher, as part of canonical URLs. It just works with whatever you’ve set as your siteurl.

    Reply

  9. Thanks for the update.

    So, enforce-www is not needed for wp 2.3+?

    I tested both variations of a page and both have the line in the source.

    Reply
  10. Pingback: WP-SuperCache, nueva versión 0.6 | aNieto2K

  11. Yay, I was waiting for a release note, but decided to upgrade it anyway. I trust you completely, Donncha 🙂

    Keep up the good work and thanks for developing this wonderful plug-in

    Reply

  12. Mvug – Super Cache has that code in it so you should see an even bigger improvement if you use it.

    cachemoney – yes, I had forgotten the canonical code that redirects automatically. Unfortunately there are a huge number of WordPress blogs who haven’t upgraded. There are even some very prominent Irish bloggers who haven’t ugpraded. I’d really hate to see them hacked.

    Denis – I haven’t tried it yet but then again I’m sure there must be people running it on 2.5 blogs by now and I haven’t heard any complaints!

    Reply

  13. Thank you very much for the effort in improving this excelent plugin!

    But regarding this:

    * The .htaccess is not updated until the user clicks a button in the backend now.

    I don’t see how to do it :-O

    That would be a very useful feature to those that have to edit the RewriteRules as the default ones are not valid for them… I have this problem with the RewriteRules:

    http://wordpress.org/support/topic/146443

    It would be great if that could be fixed in future versions 🙂

    Reply

  14. Super Coco – you need to remove the existing rules because the script isn’t smart enough to update old Super Cache rules. Then you’ll see an Update button.
    I need to investigate that a bit more. The rules that are there work for some people, but not all.

    Reply
  15. Pingback: Daily Links | Akkam's Razor

  16. Hey I am a fan of WP-Super-Cache, when I got 20000 IP/day last week, my server was as fast as normal!

    Thanks very much!

    If you need a translation for Simplified Chinese, feel free to contact me 🙂

    I also maintained the Simplified Chinese translation of Firestats.

    You are really doing wonderful jobs 🙂

    Reply

  17. Hello,

    My blog is making more and more visits and I’m afraid I would risk to reach the limits of my mutualized hosting – bad luck is my host has a limit of 400k server hits per day, I never imagined I’d risk someday to reach that limit.

    Could you tell me if SuperCache is likely to reduce the number of hits ?

    I do not know if SuperCache will gather all the php files composing my template (they are my main source for server hits, 7 php files composing the template’s structure means each visitor causes a minimum of 7 hits) into just one html file, or if it is caching data in a different way…

    Thanks if you could clarify this, Donncha 🙂

    Oliver

    Reply

  19. I run WP-Cache Manager but I’d like to try WP-Super Cache in my blogging network. Two questions.

    1. I have a plugin that counts the number of times each post is read, it will not work anymore? See, I’m not interested in those metrics, thew are not accurate, I just use that plugin to make a list of “most read last x days”.

    2. Landing sites plugin — a way of telling Google visitors about my pages related to their search — will work or not?

    Thanks

    Reply
  20. Pingback: links for 2008-03-16 « 11Pixels

  21. Donncha, with every release I salivate more and more but I continue to resist temptation because Spam Karma2 has made spam a non-issue. Any idea when Super Cache will be SK2 compatible?

    Reply
  22. Pingback: Sharing Quality » WP-SuperCache, nueva versión 0.6

  23. Jacob – SK2 will have to be modified by it’s author to use Javascript to fetch the payload it uses and update the db using an AJAX type mechanism I’m guessing. That’s one (minor IMO) disadvantage of serving completely static html files. No PHP is ever executed.

    Paulo – if it uses PHP on each request then it won’t break. It’s simple to use Javascript to do the same thing. I’ve always used javascript here, even before I started work on this plugin.

    Reply

  24. Donncha, thanks. Now I will figure how to “convert” those plugin’s actions to js. I can do a few things with PHP, but I’m a 0,0001 with Javascript. And I’m going to use SuperCache in some other blogs and websites I run with WP.

    Reply

  26. Keith – possibly but I hope that blog isn’t visible on the Internet because it’d be a juicy target for hackers! You would be much better off upgrading to the latest version of WP, please! 🙂

    Reply

  27. I want wp-postviews work normaly. How could I do that?
    How to make [?php if(function_exists(‘the_views’)) { the_views(); } ?] not change with “20,981 views” ?
    So if visitor going to my blog they’ll count normaly with wp-postviwes.
    Thanks alot. Wp-SuperCache is the best.

    Reply

  28. Rosyidi – it won’t work because it requires PHP to run. You’ll have to disable the supercache part and enclose that code in WP-Cache’s non-caching commands, or use Javascript which is what I with collecting stats. (view source if you’re interested in that code!)

    Reply

  29. where is I can found WP-Cache’s non-caching commands. I’ve view wpsupercache source, but I do’nt know where is it.
    Thanks for your reply

    Reply
  30. Pingback: J’s blog » Blog Archive » Catch blogging, expect more frequent updates now that the server is faster!

  31. Hi mate,

    im looking forward to use your super-cahce plugin since wp-cahce2 has some (small problems) when it comes to caching. Also please note that the current version 0.6 gives me a 404 at the wordpress plugin database site.

    Cheers!

    Reply

  33. Donncha,

    Thanks for this plugin. My site was crawling prior to installing your Super Cache plugin. Wow. It’s good now. Just one very, very minor point. In your instructions at the WordPress Plugin Directory, #6 says, go to Options->WP Super Cache. It should be Settings->WP Super Cache with the redesigned Dashboard.

    Reply

  34. Hi and thanks for this great plugin.

    Is there a way to force not to cache pages from search engines? (ie: do not cache/generate pages referred by Google)

    Reply

  35. Hi,

    Great plugin but I have a small problem with the htaccess file in the root of wordpress. your plugin creates the mod rewrite code in the htaccess fine. But when I try to login to the admin area or register area the formatting (css) has gone and the I get a 404 when i hit submit.

    Any ideas?

    here is my htaccess file:

    ### Restrict access to your wp-config.php file so it can’t be read if installation messes up ###

    Order Deny,Allow
    Deny from All

    # BEGIN WordPress
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    # END WordPress

    # BEGIN WPSuperCache

    RewriteEngine On
    RewriteBase /
    AddDefaultCharset UTF-8
    RewriteCond %{REQUEST_URI} !^.*[^/]$
    RewriteCond %{REQUEST_URI} !^.*//.*$
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} !.*s=.*
    RewriteCond %{QUERY_STRING} !.*p=.*
    RewriteCond %{QUERY_STRING} !.*attachment_id=.*
    RewriteCond %{QUERY_STRING} !.*wp-subscription-manager=.*
    RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz -f
    RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html.gz [L]

    RewriteCond %{REQUEST_URI} !^.*[^/]$
    RewriteCond %{REQUEST_URI} !^.*//.*$
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} !.*s=.*
    RewriteCond %{QUERY_STRING} !.*p=.*
    RewriteCond %{QUERY_STRING} !.*attachment_id=.*
    RewriteCond %{QUERY_STRING} !.*wp-subscription-manager=.*
    RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress|wp-postpass_).*$
    RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f
    RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html [L]

    # END WPSuperCache

    Reply

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.

Close