Support » Plugin: WP Super Cache » Issue with preloading

  • Hello,
    I’ve got an issue with the preloadind mode using the latest version of WP Super Cache (1.5.9).
    It’s actually preloading all my URL as expected and as it used to do before, but all of a suden, near the end of the preloading, while it has preloading all the posts and preloading the last pages, the garbage collection starts and actually deletes all the URL that just got preloaded.
    Here is an extact from the debug log

    
    21:27:00 8968 /wp-cron.php?doing_wp_cron=[...] clear_post_supercache: deleting files in /home/wp/wp-content/cache/supercache/url.fr/
    21:27:00 8968 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: deleted /home/wp/wp-content/cache/supercache/url.fr/bloglist-et-liens/index-https.html
    21:27:00 8968 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: deleted /home/wp/wp-content/cache/supercache/url.fr/bloglist-et-liens/index-https.html.gz
    21:27:00 8968 /wp-cron.php?doing_wp_cron=[...] gc: deleted /home/wp/wp-content/cache/supercache/url.fr/bloglist-et-liens, forced delete
    21:27:00 8968 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: deleted /home/wp/wp-content/cache/supercache/url.fr/test4/index-https.html
    21:27:00 8968 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: deleted /home/wp/wp-content/cache/supercache/url.fr/test4/index-https.html.gz
    21:27:00 8968 /wp-cron.php?doing_wp_cron=[...] gc: deleted /home/wp/wp-content/cache/supercache/url.fr/test4, forced delete
    [...]
    21:29:02 8987 /wp-cron.php?doing_wp_cron=[...] wp_cache_get_cookies_values: return:
    21:29:02 8987 /wp-cron.php?doing_wp_cron=[...] In WP Cache Phase 2
    21:29:02 8987 /wp-cron.php?doing_wp_cron=[...] Setting up WordPress actions
    21:29:02 8987 /wp-cron.php?doing_wp_cron=[...] Not caching wp-admin requests.
    21:29:11 8987 /wp-cron.php?doing_wp_cron=[...] wp_cron_preload_cache: doing taxonomy preload.
    21:29:11 8987 /wp-cron.php?doing_wp_cron=[...] wp_cron_preload_cache: got 100 posts from position 100.
    21:29:11 8987 /wp-cron.php?doing_wp_cron=[...] wp_cron_preload_cache: clean expired cache files older than 86400 seconds.
    21:29:11 8987 /wp-cron.php?doing_wp_cron=[...] Cleaning expired cache files in /home/wp/wp-content/cache/
    21:29:11 8987 /wp-cron.php?doing_wp_cron=[...] Doing GC on supercache dir: /home/wp/wp-content/cache/supercache
    21:29:11 8987 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: did not delete file as it wasn't a directory or file and not forced to delete new file: /home/wp/wp-content/cache/supercache/url.fr/contact/index-https.html
    21:29:11 8987 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: did not delete file as it wasn't a directory or file and not forced to delete new file: /home/wp/wp-content/cache/supercache/url.fr/contact/index-https.html.gz
    

    So once preloading is finished, I left in my cache with only the few pages that had not been preloaded yet and are about to be preloaded after this garbage collection.

    If I compare with the behavior using WP Super Cache 1.4.9 (I kept this one for quite a while seeing the various issues with the 1.5.x versions), here is how the debug log file looked like:

    
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] wp_cron_preload_cache: doing taxonomy preload.
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] wp_cron_preload_cache: got 100 posts from position 100.
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] wp_cron_preload_cache: clean expired cache files older than 86400 seconds.
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] Cleaning expired cache files in /home/wp/wp-content/cache/
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] Doing GC on supercache dir: /home/wp/wp-content/cache/supercache
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: did not delete file as it wasn't a directory or file and not forced to delete new file: /home/wp/wp-content/cache/supercache/url.fr/bloglist-et-liens/index-https.html
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: did not delete file as it wasn't a directory or file and not forced to delete new file: /home/wp/wp-content/cache/supercache/url.fr/bloglist-et-liens/index-https.html.gz
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: did not delete file as it wasn't a directory or file and not forced to delete new file: /home/wp/wp-content/cache/supercache/url.fr/test4/index-https.html
    21:17:12 8560 /wp-cron.php?doing_wp_cron=[...] prune_super_cache: did not delete file as it wasn't a directory or file and not forced to delete new file: /home/wp/wp-content/cache/supercache/url.fr/test4/index-https.html.gz
    

    When it went through the garbage collection, it didn’t delete the preloaded file.

    Here is the WP Super Cache configuration that I’m using :
    – Cache Delivery Method : Expert
    – Don’t cache pages for “Logged in users and those that comment
    – Compress pages so they’re served more quickly to visitors.
    – Extra homepage checks. (Very occasionally stops homepage caching)
    – Only refresh current page when comments made.
    – List the newest cached pages on this page.

    The very same kind of issue as already been reported here : https://wordpress.org/support/topic/preload-of-custom-taxonomies/#post-9735319

    Let me know if I can provide any more information on this issue. Preloading is a very valuable feature of this plugin, so that would be fantastic if it could work again as it used to for years 🙂
    Thanks of lot.

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Issue with preloading’ is closed to new replies.