UPDATE! I have just updated the plugin version number to 1.2. Thanks to everyone who tested it!
A new version of WP Super Cache is
almost out and here are the changes in this full page caching plugin for WordPress. OH! Hang on. Almost out? Yeah. I’m going to release it tomorrow but I would love a couple of hardy folks to try it first. People on the forums have been using the development version for several weeks without incident but I would really appreciate it if a few more tried it before the general public gets it. You know what to do, I don’t need to explain. Here’s wp-super-cache.zip. This is the version running on this very site right now and it’s very stable. Go at it! I’ll update this post in the morning, UTC. Thanks.
So, those changes eh?
- Garbage collection of old cache files is significantly improved. I added a scheduled job that keeps an eye on things and restarts the job if necessary. Also, if you enable caching from the Easy page garbage collection will be enabled too.
- Editors can delete single cached files from the admin bar now. (thread)
- Fixed the cached page counter on the settings page (thread)
- Some sites that updated to 1.0 experienced too much garbage collection. There are still stragglers out there who haven’t upgraded but that’s fixed now! (thread)
- Supercached mobile files are now used as there was a tiny little typo that needed fixing. (thread)
- If your site is in a directory and you saw problems updating a page then that should be fixed now. (thread)
- The deactivate hook has been changed so your configuration isn’t hosed when you upgrade. Unfortunately this will only happen after you do this upgrade.
- Some sites use custom cookies with the LOGGED_IN_COOKIE constant. Added support for that.
- Added support for WPTouch Pro, but it appears to be flaky still. Anyone have time to work on that? I don’t.
- Some sites had problems with scheduled posts. For some reason the plugin thought the post was in draft mode and then because it only checked the same post once, when the post magically became published the cache wasn’t cleared. That’s fixed, thanks to the debug logging of several patient users.
- And more bug fixes and translation updates.
You might also like