I can confirm this, but with your site it also happens to me with firefox.
I got the very same problem with my site. The cache generation is working, files are stored, etc., but the pages are generated again each time, with a new timestamp in the source code.
It’s driving me crazy, because I had that problem some time ago, then fixed it by installing the development version.
Now it’s broken again, and I didn’t change anything super cache related.
btw., with the newest developer version from today I get an error in the admin interface:
Warning: filemtime() [function.filemtime]: stat failed for /www/htdocs/w0082362/xxx/wp-content/cache/supercache/xxx.com in /www/htdocs/w0082362/xxx/wp-content/plugins/wp-super-cache/wp-cache.php on line 1396
both of you – try the dev version (laviolette99) on the download page and delete the SUPERCACHE rules in your .htaccess. The plugin will regenerate them if you tell it to then. That may be the bug you’re seeing.
marclorenz – I’ve fixed that filemtime warning, but it’s harmless so I just hid it. Did you delete the .htaccess rules before trying the dev version?
Hi Donncha,
I deleted everything WP Super Ccache related on the sever, including the htaccess rules, then uploaded the latest dev version.
It seemed to do the trick…Thanks for the suggestion!
I don’t know if you changed something in the latest version, or if I missed something before, but right now it’s working perfectly with super cache!
I couldn’t imagine using wordpress without your plugin, because it’s just too slow then, IMO it should be part of the core.
You’re doing a great job here, I know how to throw together some PHP, but I can’t even imagine how this one works!
Thanks again,
Marc
Hi Donncha,
I’ve uninstalled everything and tried the dev version, but I still have the same issue.
When I first tried it after installing the plugin, I thought it was working fine, but after closing and reopening the browser, I realized that I had the same issue.
The dev version says version 0.9.6.1. Do I have the correct version?
Here are the rules I now have in my .htaccess file:
# BEGIN WPSuperCache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
AddDefaultCharset UTF-8
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP_USER_AGENT} !^.*(Android|2.0\ MMP|240×320|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|hiptop|IEMobile|iPhone|iPod|KYOCERA/WX310K|LG/U990|MIDP-2.0|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|Playstation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|Windows\ CE|WinWAP).*
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_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_).*$
RewriteCond %{HTTP_USER_AGENT} !^.*(Android|2.0\ MMP|240×320|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|hiptop|IEMobile|iPhone|iPod|KYOCERA/WX310K|LG/U990|MIDP-2.0|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|Playstation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|Windows\ CE|WinWAP).*
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html [L]
</IfModule>
# END WPSuperCache
🙁
Thanks,
S.
Those rules look fine. Is the blog installed in / ? Have you tried it in half-on mode? That’s 99.99999% (ie. practically as fast) as fast as full mode.
What do you mean installed in “/?” ?
Tha half mode works but this blog has spikes of tens of thousand visitors per hour. That’s why we’re looking for the most robust solution.
Donncha,
I think I found what’s causing the problem, but I can’t solve it…
The permalink structure we’re using is like the following: http://www.wordpointer.com/sync/2009/09/halo-3odst-game-review-its-finally-here.html
We recently imported this blog to WordPress from an other plateform, and we had to insert the “/sync/” in the middle of the permalink structure to preserve the original post urls. For obvious SEO reasons, we can’t change that (we have over a thousand posts).
Do you know how I could tell the plugin/cache directory/htaccess file to look for this structure for post and category pages? The homepage does not have that…
Thanks a lot for your support!
Check your wp-content/cache/supercache/www.wordpointer.com/ directory. Is there a “sync” directory there? If so change the two lines that serve the cache file (index.html and index.html.gz) that look like this:
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html
to
RewriteRule ^(.*) /wp-content/cache/supercache/%{HTTP_HOST}/sync/$1/index.html
Note the extra sync? Do the same for the index.html.gz line too..
The sync directory is there and it has cache pages in it, but it doesn’t work with the sync in the rewrite rule.
I also tried to change that line:
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{HTTP_HOST}/$1/index.html -f
(-:
I nailed down the bug….
There was a directory named “sync” under my main domain directory!
Thanks for your support!
