Well, the new WP Super Cache is available now.
This release adds experimental object cache support. Don’t go looking for it unless you have an external object cache already. It won’t show up. I recommend using the Memcached object cache.
Some of the other major changes include more translations: Chinese (Pseric), Ukranian (Vitaly) and Japanese (Tai). The Italian and Japanese translations have since been updated but not included in 0.9.9. You can grab them from the languages directory if you don’t want to wait until the next release.
If you have WordPress Mobile Edition installed the plugin will grab the list of mobile user agents from that and warn if your .htaccess is outdated.
And, a small but significant change is that the PHP cache loader will use the static “super” cache if necessary. This might happen if your rewrite rules aren’t working properly and not serving cache files. At least your anonymous visitors will see some sort of cached file. Use the debugging system built into the plugin to determine where the cache comes from.
See the changelog for the complete list of changes.
28 thoughts on “WP Super Cache 0.9.9”
As the version approaches 1.0.0, what changes should it make?
new version works great even the object cache addition. i am just wondering if we will have the choice of caching for logged in users in the future?
and will there be a way to use default permalinks? i don’t want to change mine
Default permalinks with the object cache? Maybe, although why anyone would willingly use those is beyond me! If you use a custom permalink the ?p=X format will redirect to the correct post.
It’s doubtful the object cache caching will ever support logged in users because of the way it works. Still, they’re a tiny minority of most sites.
i will attempt the custom link you are talking about. i admit i don’t understand how any of this works. i just have always left it on default url and if i change i am afraid of losing all my links on google, ect ect
but here is why i was looking for logged in cache.
i run an american idol. on results nights i can have anywhere from 800 to 1600 people online. many of which are logged in users. all of which are refreshing the posts looking for the newest information on who went home.
i really want to use the memcache aspect as I have a huge memcache server that I have access to but i think having this unchecked allows me the best stability for when i will need caching the most.
If it’s one server then just use supercache normally. Your filesystem will cache any files anyway.
I’m on shared hosting, how to enable Object cache?
Kells – unfortunately you won’t be able to as you probably need to be root to install any of the object cache backend engines.
First I have to say that I am a newbie when it comes to this.
Here is what happened I installed WP cache on my website. I thought I did everything right, but I received an email from Go daddy telling my that they were going to suspend my accoung because of the CPU. I have one month to get this sorted out, but to be honest I have no clue how to properly uninstall WP super cache.
I truley am scared that I am going to screw something up when I uninstall it.
I am desperate at this point for any help, as to how to do a clean uninstall.
P.S I’m on a shared hosting site.
Thank you in advance for your help and your time.
Michele – read the readme.txt, it’s all in there. You’ll want the “If all else fails” section.
Thanks so much for the fast reply. I appreciate it so much. Your site is a God send.
Here is what I did: I had this in the root directory .htaccess
Could this cause a problem?
`# END supercache`
I removed the second part and now I have that in the wp content/cache/.htaccess
Would this cause violation in my CPU usage?
Thanks again for your help 🙂
No, it wouldn’t. It’s more than likely another plugin that’s causing the CPU hike. I couldn’t tell you what ones are responsible, but try disabling them one by one and reloading your blog without Supercache and note when the page takes longest.
I’d like to ask a few questions if I may:
1. my site is Page-centric. Does Super Cache work on Pages, or just posts?
2. in the installation instructions, it says php safe mode must be disabled, but it doesn’t say how to do that.
3. step 7 of the installation says “mod_rewrite rules will be inserted into your .htaccess file. Look in your web root directory for this file.”
by “web root directory” do you mean the true root, or the WP root? Also, not to be too picky, but you don’t suggest a corrective action if this isn’t here.
Thank you. I’m excited about using this plug-in if I can get the above issues worked out.
1. Yes. It works with pages too.
2. Use Google to find out. That’s documented in the PHP manual and lots of other places.
3. It should be in the web root, the base directory where your blog lives. You’ll almost always have a .htaccess file if you have custom permalinks enabled. (which is a requirement for this plugin)
Hi! After I upgraded to version 0.9.9. My site turns out just white pages.
html body area doesn’t include anything.
Can you guess any reason?
Someone else is having the same problem. Can you contribute to the thread here and try out the debug function to see what the plugin is doing on your site?
Version 0.9.9 doesn’t play nicely with WordPress mobile widget: had to turn off the cache plug-in because it was preventing some content from displaying.
Today I un-installed the wp super cache. But after un-installation(removed all folders/files which has created by wp super cache). I couldn’t visit to any link of my blog, even feed url. It says page not found! I only can see my blog home page. It was a disaster after un-installing wp super cache.
How to fix?
Follow each step of the “If All Else Fails” section of the readme.txt and your site will be ok.
I want to set different expire time for my site, for example home, tag, category page should expire in hour and single post and pages should expire once a day. how to do that?
Unfortunately you can’t. It’s all the one expire time.
We came across some weird behavior, not sure they’re isolated issues or not, assuming so as others haven’t mentioned them.
We noticed that different browsers serves up different cached versions (different time stamps). For example, Firefox, Chrome and Safari all show different time signatures in the “Cached page generated by WP-Super-Cache on [time here]” part….not sure if it is normal and only noticed because we realized our expire time ( 3600 seconds) is not expiring, or at least old files don’t seem to be deleted via garbage collection.
If we view “List Cached Files” we see “Stale” files listed with ages of 8600, 10200, etc….. This persists if we clear browser cache and cookies. If we lower expiration to say, 60 seconds, there is no issue, it expires as it should. We reinstalled with no luck… so cached pages stay cached indefinitely….
On a side note, another minor issue we noticed is that “Don’t Cache Pages for Logged in Users” seems to work unless you are in Safari….
Any feedback appreciated on why Garbage collection might not be occurring as expected!
Are there any instructions for the best way to upgrade on WPMU? Is it best to deactivate supercache entirely and reinstall from scratch, or is it sufficient to overwrite the files?
Hey all, I maintain our school site. It uses WordPress to great effect. I had heard there were a few problems with earlier versions of Super Cache. At present we don’t have a caching plugin installed, but because WordPress memory usage is going through the roof recently (fluctuating between 50-85% daily) I was thinking about installing this plugin. Have any of you had problems with it? Or would you know how to solve the memory usage problem – unfortunately I’m not that technically minded. Thanks in advance, Chris
I’ve found that your plugin creates a cached page for each individual logged in user, for each page they visit within the garbage collection window. So if i have 10 users logged in and looking at the same page, they are all rendering a cached version each. This surely defeats the point of caching, as they are unlikely to look at the same page twice.
Is there a setting I can change so that it caches a version of each page when visited by a logged in user per role – not per user?
So all subscribers get the same cached page served to them, and all admins get their own cached page etc.
I love your plugin and it works a treat for anonymous visitors, but my site has quite a few members and page render time is becoming annoying.
Happy to make a donation for a solution.
Michael – unfortunately the plugin needs to make separate cache pages per logged in user because the page usually has personal data like comment name, email and web address on posts.
Unfortunately I don’t have any plans to change this but the idea of caching by user role is interesting. You would have to make sure that your posts don’t have comment forms because people will see the personal details of other users.
You could also disable caching for “known users”, at least then the overhead of all those files is avoided.
Michael – you should also look at caching MySQL queries with db cache reloaded, or memcached. That will probably make things faster for logged in users.