WordPress.org

1. deanpence
   Member
   Posted 1 year ago #

   Hi, I'm having a bit of a confusing problem with WP Super Cache: Supercache files are not being generated at all.

   (Side note: I recently configured nginx to properly serve static Super Cache files, but that shouldn't be relevant.)

   Useful info:

   • Without a primed cache (i.e., after deleting the cache), I get this:
     • At the bottom of the page:
       

       <!-- Dynamic page generated in 0.343 seconds. -->
       <!-- Cached page generated by WP-Super-Cache on 2010-08-01 19:14:47 -->

     • In headers, nothing related to WP-Cache or WP-Supercache.
   • After the first request (presumably when the cache should be primed), I get this:
     • At the bottom of the page:
       

       <!-- Dynamic page generated in 0.343 seconds. -->
       <!-- Cached page generated by WP-Super-Cache on 2010-08-01 19:14:47 -->
       <!-- Compression = gzip -->

     • In headers: WP-Super-Cache: WP-Cache

   Here's my setup:

   • nginx 0.8.46 (running as web:web)
   • php-fpm with php 5.3.3 (running as web:web)
   • WordPress 3.0.1
   • WP Super Cache Config:
     • WP Super Cache Status:
       • ON
       • Cache Rebuild.
       • Mobile device support (merely to get rid of the notice)
     • Super Cache Compression: Enabled

   All directories are owned by web:web.

   The "Cache Contents" reports that nothing is cached by either WP-Cache or WP-Super-Cache.

   Other plugins:

   • Akismet 2.3.0
   • Audio Player 2.0.4.1
   • FancyBox for WordPress 2.7.2
   • fbLikeButton 0.4a
   • FeedBurner FeedSmith 2.3.1
   • Google Analytics for WordPress 4.0.6 (with '#' instead of '?' for tracking)
   • Google XML Sitemaps 3.2.4
   • ShareThis 3.2

   http://wordpress.org/extend/plugins/wp-super-cache/

2. deanpence
   Member
   Posted 1 year ago #

   Thanks in advance for any help, by the way. This plugin actually helps me to host my customers at probably half the cost, even without static files.

3. Donncha O Caoimh
   Member
   Posted 1 year ago #

   There's probably something up with your Nginx rules. Unfortunately I've only used Nginx once and have since gone back to Apache so can't help you there. :(

4. deanpence
   Member
   Posted 1 year ago #

   It's a pity that such a great web server has such poor documentation and unintuitive configuration syntax.

5. deanpence
   Member
   Posted 1 year ago #

   I haven't dug around in the source code yet, but does the plugin refuse to write out supercache files when it can't verify mod_rewrite is in use?

   The only times I can get WP Super Cache to write supercache files is by the cache tester and preloading. But I'm hesitant to use preloading if the supercache files will never get regenerated.

6. deanpence
   Member
   Posted 1 year ago #

   I've found the answer to part of this, and it's listed on the very beginning of your readme file:

   [B]ecause a user's details are displayed in the comment form after they leave a comment those requests are handled by the legacy caching engine.

   I was expecting supercache files to be generated even when I was logged in (I had "Don’t cache pages for known users" unchecked), but the plugin does not generate them when it uses legacy caching (i.e., when certain cookies exist). I started using another browser to browse as an anonymous user, and whenever I browse to them, supercache files are generated as expected.

   There still seems to be a problem with preloading, however. When I enable preloading and enable a small refresh interval (e.g., 5 minutes):

   1. The refresh interval is never saved. (I have to edit wp-cache-config.php and edit $wp_cache_preload_interval manually.)
   2. No pages ever get preloaded until an anonymous user browses to them. (I've checked my logs to make sure wp-cron.php is getting called, and it is.)

   Thoughts?

Topic Closed

This topic has been closed to new replies.