I’ve been using WP SuperCache on my WPMU 2.8.4 blog for a while and it works great there. I just upgraded the blog to WP 3.0.2 and noticed some strange behavior in WP SuperCache. FYI, I’m using the mod_rewrite method for WP Super Cache.
In WP 2.8.4, WP SuperCache would create 2 cached versions of the home page when a user first visited it: /vol/www/www.mysite.com/blog/index.html and /vol/www/www.mysite.com/blog/index.html.gz. So the next time a user loaded the home page, Apache would just load the HTML or, even better, the gzipped HTML from the cached files.
Since we’ve upgraded to WP 3.0.2 and upgraded WP Super Cache to the latest version, the webserver isn’t creating the correct cached HTML pages for the home page. Rather than creating /vol/www/www.mysite.com/blog/index.html and /vol/www/www.mysite.com/blog/index.html.gz, the webserver is creating 2 temp files each time it loads the page. Here are some examples: /vol/www/www.mysite.com/blog/10081128374cf92a47699b86.32924954.tmp and /vol/www/www.mysite.com/blog/10081128374cf92a47699b86.32924954.tmp.gz.
This behavior causes 2 problems. First, the home page loads more slowly. Second, and perhaps even more importantly, my cache directory is quickly getting filled with useless files that may ultimately create some kind of problem with the linux server.
FYI, WP Super Cache seems to be working just fine in creating the cached versions of articles or custom pages. The only problem seems to be with archive pages such as the home page.
Any help you could provide would be greatly appreciated!
- The topic ‘WP Super Cache isn't caching archive pages correctly’ is closed to new replies.