WP Super Cache version 0.8.3 is now available. WP Super Cache is a page caching plugin for WordPress that will significantly speed up your website.
Double Caching
This releases fixes a long standing compression bug. In older versions of the plugin, the cached page was compressed twice. Once to display to the current visitor, and once again for the cached files stored on the server. This has now been fixed and there’s a noticeable speed increase for anonymous visitors. Unfortunately as a side effect, it’s not possible to display the “super cache gz” html comment now. To verify that html pages are being served from the supercache directory you’ll have to add an error_log() somewhere and check that visits aren’t logged.
The plugin now uses fopen() instead of gzopen() which according to a comment on the gzopen() manual page is unreliable under high load.
IE7 Fixes
Apparently IE7 has problems when gzipped files are served as “x-gzip” files, under certain circumstances. This is an obscure bug but this has been fixed. If you’re upgrading, either remove wp-content/cache/.htaccess and visit the admin page and that file will be regenerated, or edit that file and change “x-gzip” to “gzip”.
A number of smaller bugs were also fixed. Check the changelog for further info.
24 Comments
Neil (10 comments.) on October 8, 2008 at 8:30 pm.
Id love to use this plugin, but im not sure after past failures. How can i test if the plugin is really spitting out cached files?
Satranç (1 comments.) on October 8, 2008 at 9:29 pm.
Nice work, are you planning to integrate widget cache?
Thank you.
Dan (1 comments.) on October 8, 2008 at 9:51 pm.
I’ve been using your plugin since it was released, and I really appreciate it. Thanks for the update!
Irwan.biz (1 comments.) on October 8, 2008 at 9:59 pm.
too bad that I still don’t have the chance to use it. My traffic is so poor
Nicki (1 comments.) on October 8, 2008 at 11:48 pm.
YAY! Thank you, Donncha!
Joel (2 comments.) on October 9, 2008 at 6:22 am.
Hi thanks again for another wonderful update for my favorite plug in. Keep up the good work
this plug in is a life saver for me.
George Serradinho (2 comments.) on October 9, 2008 at 9:53 am.
Thanks for the update, keep up the good work.
Matt on October 9, 2008 at 1:36 pm.
Many thanks for the updates Donncha.
I did notice my .htaccess in the cache folder didn’t update, so I deleted it. Deactivated / activated, visited the admin page, but the file was not re-created until I tuned the cache fully on.
Also, I have noticed a long time bug. “No Adverts for Friends plugin is enabled.”. When I click “Disable” nothing changes.
Thanks again!
Pingback: WordPress 2.7 1st Impressions-A Snappy Admin. | Green Mountain Geek
ghprod (1 comments.) on October 9, 2008 at 11:51 pm.
i want to use ur plugin in my site … bcoz my hosting use shared server ….i think is wise to use this plugin to reduce server load ..
Thnx for hard work
www.ithoughts.de (1 comments.) on October 10, 2008 at 8:30 am.
Indeed, thanks! My server’s not the fastest in the world and I really appreciate your work.
Aw Guo (1 comments.) on October 10, 2008 at 3:05 pm.
I am just curious that what is the detail differences between gz-output and non-gz-output.
Will the compression really save a lot of time comparing to the non-compression one? How long (time) will it save about? 10% or 50% ?
seolamo :) (1 comments.) on October 10, 2008 at 5:48 pm.
Working good, thanks for update. 7000 hosts/24 h.
Binh Nguyen (3 comments.) on October 13, 2008 at 4:56 am.
I’m very happy whenever you fix a bug because I like Wp-Super_Cache very much.
However, I’m still not using it because the issue of not being able to turn it on/off for each blog instead of the whole site is still there. Did you manage some time to look into the issue? I wrote a request on wordpress forum.
Thanks.
Joss Winn (1 comments.) on October 13, 2008 at 5:17 pm.
I set up eAccelerator today before looking at this plugin. Are they basically doing the same work? Do you have any thoughts on how they compare?
Thank you
Joss
Donncha (1707 comments.) on October 13, 2008 at 9:08 pm.
Binh – look at the threads you opened as I and others have given you instructions on that.
Joss – No, they’re doing different jobs. You should install both!
Joss Winn on October 13, 2008 at 9:18 pm.
Great. I need all the caching I can get! Thanks.
Pingback: WP-SuperСache: БыÑтрей! Еще быÑтрей! - Lecactus Home
Jonathan (1 comments.) on October 16, 2008 at 4:24 am.
I’m trying to display the latest post from WP (/blog/ on the site) on the site’s homepage, and I’m finding that when WP Super Cache and the gzip option are both enabled, I get the gzipped binary output of the post, instead of the plain-html I’d like to display.
Is there a way to tell the plugin not to serve the gzipped version on a one-off basis?
Thanks!
Donncha (1707 comments.) on October 16, 2008 at 4:35 am.
Jonathan – why not use the feed instead to get the first post?
Scott on October 21, 2008 at 9:21 pm.
This sounds like an amazing plugin,and I have been reading about it all day without actually installing it just yet. Does anyone know if installing this, since it generates a static html file, it is likely to cause server problems under heavy traffic? I know this is a very broad question, but if anyone has any experience, it would be very appreciated.
Jonathan on October 23, 2008 at 2:23 pm.
Didn’t want to use the feed because I want to add special formatting. I suppose it’s possible via xslt on the feed’s xml… I’m just stuck in my programmer ways… wanted to use the wp functions to get at it.
Thanks for the idea.
Michael Aulia (9 comments.) on October 24, 2008 at 12:28 am.
Scott: It only generate a static HTML on the first time someone gets to the page. Afterwards, it’s a pure static HTML served to visitors. It saves lots of CPU usage from PHP calls.
Donncha: Can’t find the latest changelog post on your blog? (version 0.8.4). I hesitate to upgrade if I don’t know what’s changed
(who knows when things stop working hehe)
Donncha (1707 comments.) on October 24, 2008 at 11:04 am.
Michael – I didn’t bother making a post as it’s only a small change to how the expired files are cleaned up. I added a time check instead of the hits check. May post about it today I guess.