WP Super Cache 0.9.9.2 has just been released! This version works with WordPress 3.0 and adds a number of new features and bug fixes:
- Cache Preloading will cache every post on your site.
- A cache tester that will check if your homepage is cached.
- Much better support for mobile plugins.
- Mod rewrite rules can now be updated from within the admin page.
- Lots and lots of bugs fixed. See the changelog for more details.
Preloading creates lots of files on your server so if you have many thousands of posts please be aware of this. Filesystem limitations may cause problems if you use a flat permalink structure. For example, ext2 or ext3 only allows 32,000 directories in a directory. If you have more than that number of posts you may run into problems.
The plugin does not preload category or tag pages but because your single posts will be cached you’ll find the load on your server will be reduced. Uncached pages will be served more quickly and your visitors will have a quicker and better experience on your site.
You may also see an increase in site traffic if your server was previously underpowered!
Update! I just released 0.9.9.3 to address the (mostly minor) bugs that were reported overnight. If you don’t notice anything wrong there’s no need to upgrade.
Hi, trying to figure out how to reset the cache after saving menu (WP3.0 menu)
tested without success the following in wp_cache_phase2
add_action(“admin_menu” , ‘ prune_super_cache’ );
any idea ? this would be nice to avoid the extra step of manually clearing the cache after editing
OK tried this one
add_action(“wp_update_nav_menu” , ‘ wp_cache_clear_cache’ );
reacts OK but error message :
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘ wp_cache_clear_cache’ was given in /home/polewest/www/wp-includes/plugin.php on line 395
OK Problem sorted , stupid typo mistake
more here http://www.webmasterbulletin.net/2010/07/wp-super-cache-and-wp3-0-menus/1270
Is there any reason for the comment in the source to say ‘Dynamic page generated in -0.83 seconds’
Note the ‘minus’ sign.
Duplicate process: I’ve updated a previously cached post and visited (almost immediately) it on a different browser with no cookies or history.
When I visited that page after a minute or so, it is showing the same ‘-0.83 seconds’.
All other pages are showing a positive number (that is with no sign at all).
Todd – that’s some weird server you’ve got there, heading back in time and all that! I don’t know why you’d get a negative number there as it’s a counter and can’t be negative! You might have to dig into the source and find out for yourself.
Hi Donncha,
Am I correct in thinking that SC does not automatically generate a new cached home page after a new post is posted?
If it does not, that may be an enhancement to consider. Google arrives usually within 30 seconds of being pinged and it would be great if it met a cached home page and a cached page for the new post.
Many thanks,
Danny
Yes, it doesn’t. You can write a plugin that hooks into the publish_post action and fetches the front page of your blog if you really want it to be cached immediately.
A couple of questions (any help is appreciated):
1. I’m seeing this error under “Directly Cached Files”. Warning! /xxx/xxx/xxx/xxx/xxxxx/
domains/exampledomain.com/html/ is writable. Please make it readonly after your page is generated as this is a security risk.
Since I have the CHMOD set to 750, I believe the permissions are correct. Any thoughts? (Note: x’s were just added to mask the path.)
2. If I want to disable the mobile support, which part of the mod rewrite rules should be removed?
3. I’ve also got the following in my .htaccess and I’m wondering if any of these would conflict with the plugin:
#AddHandler application/x-httpd-php5 .php
AddHandler php5-script .php
Header unset ETag
Header unset Last-Modified
FileETag none
Header set Expires “Mon, 27 Dec 2010 20:00:00 GMT”
Header set Cache-Control “public, no-transform”
php_value output_handler ob_gzhandler
AddOutputFilterByType DEFLATE application/x-javascript text/css text/html text/xml
Anyway to prevent the caching of pages requested through SSL?