GC not working correctly !
-
Hello,
The garbage collection of the super cache plugin: https://ww.wp.xz.cn/support/plugin/wp-super-cache always deletes all the files and directories on the server and rebuilds both the super cache ( static pages ) and the legacy browser caches (GET parameters) regardless of any plugin back end settingsI disabled all garbage collection by choosing a cache time out value of zero seconds from the Advanced top menu under: Expiry time & Garbage collection. I also unchecked the Preload mode check box from the Preload top menu.
I checked the word press cron system and I still found a garbage collection scheduled task from this plugin: ‘wp_cache_gc’ scheduled to run ?
I am not sure why this plugin still deletes and rebuilds the cache files and directories despite of disabling all garbage collection back end settings. Please help!
Thanks!
-
This topic was modified 8 years, 9 months ago by
okfattouh.
The page I need help with: [log in to see the link]
-
This topic was modified 8 years, 9 months ago by
-
Hello,
On a separate note, I never get any emails any time the garbage collection runs even though I checked the Notification Emails check box: Email me when the garbage collections runs from the Advanced top menu under: Expiry time & Garbage collection.
The server hosting this website supports sending emails and all the emails are working for all the other sites hosted on the same server so it’s not a web host issue.
Does this plugin even work at all ?
Thanks!
Can you enable the debug log? That will tell you if the plugin is doing anything, or why it’s deleting everything.
– I enabled the debug log and the wp-cache meta files are still deleted without being mentioned in the debug log even though garbage collection is disabled by activating the preload mode and the cache timeout is set to: 604800 seconds (1 week)
– I thought this bug was fixed in the latest releases? Why is it too hard to fix ?
– These are some entries from the debug log file for one of the GET request parameters that is using the wp-cache and you will notice that the last entry mentioned in the debug log below that this meta file was written to the wp-cache while nothing is mentioned about deleting this meta file:
“Writing meta file: /wp-content/cache/supercache/staging.pshsa.ca/shop/meta-wp-cache-96b0581ec171864613782d905f99d3ea.php”– These are the full entries only for this wp-cache meta GET request:
——————————————————————-17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_get_cookies_values: return:
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_get_cookies_values: return:
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_check_mobile: staging.pshsa.ca443/shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2gzip
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 supercache dir: /wp-content/cache/supercache/staging.pshsa.ca/shop/
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_check_mobile: -https
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 No Super Cache file found for current URL: /wp-content/cache/supercache/staging.pshsa.ca/shop/index-https.html
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_get_cookies_values: return:
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_check_mobile: staging.pshsa.ca443/shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2gzip
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 In WP Cache Phase 2
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Setting up WordPress actions
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Supercache caching disabled. Only using wp-cache. Non empty GET request. {“swoof”:”1″,”pa_training-category”:”training-cat”,”pa_training”:”in-class-training”,”pa_all-courses”:”certification-part-2″}
17:52:35 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Created output buffer
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Output buffer callback
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Supercache disabled: GET or feed detected or disabled by config.
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_get_cookies_values: return:
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Gzipping buffer.
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Writing gzipped buffer to wp-cache cache file.
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Renamed temp wp-cache file to /wp-content/cache/supercache/staging.pshsa.ca/shop//wp-cache-96b0581ec171864613782d905f99d3ea.php
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Writing gzip content headers. Sending buffer to browser
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 wp_cache_shutdown_callback: collecting meta data.
17:52:53 22670 /shop/?swoof=1&pa_training-category=training-cat&pa_training=in-class-training&pa_all-courses=certification-part-2 Writing meta file: /wp-content/cache/supercache/staging.pshsa.ca/shop/meta-wp-cache-96b0581ec171864613782d905f99d3ea.phpPlease Help !
-
This reply was modified 8 years, 7 months ago by
okfattouh.
> I thought this bug was fixed in the latest releases? Why is it too hard to fix ?
I thought it was fixed too. Some bugs are hard to reproduce. I personally don’t use custom post types that don’t have a rewrite url so I don’t encounter this bug at all unfortunately. If you have a suggestion for a plugin (that uses custom post types without a rewrite url) that I can install and test with I’d love to hear it, or else I’ll write my own..
Please reply on this thread, and not the other one you created to keep things tidy.
Hello Donncha,
– Thank you so much for your reply. Sure, will only use one thread instead.
– I appreciate all the hard work you are doing and I understand that errors are sometimes very hard to reproduce.
– Currently the custom post types in the back end are:
WOOF – WooCommerce Products Filter ( no rewrite rules ):
https://ww.wp.xz.cn/plugins/woocommerce-products-filter/
Woo commerce ( using rewrite rules ):
https://en-ca.ww.wp.xz.cn/plugins/woocommerce/Regards,
Omar M.Hello Donncha,
– I don’t know if this can help but below are samples of the path to some wp-cache directories on the server which stores the GET meta files for the woo commerce product filter (?x=y):
* This is path on the server to the woo commerce products filter main shop pages:
DOC_ROOT_PATH/staging.pshsa.ca/wp-content/cache/supercache/staging.pshsa.ca/shop* This is the path on the server to the second page of the products filter:
DOC_ROOT_PATH/staging.pshsa.ca/wp-content/cache/supercache/staging.pshsa.ca/shop/page/2* This is the path on the server to the forth page of the products filter:
DOC_ROOT_PATH/staging.pshsa.ca/wp-content/cache/supercache/staging.pshsa.ca/shop/page/4– Sample of meta files stored inside these recursive directories that get deleted randomly:
meta-wp-cache-6a0664571a2f7b7a0e469d85f7a88bef.php
wp-cache-6a0664571a2f7b7a0e469d85f7a88bef.phpRegards,
Omar M.Hey Donncha,
– Is it possible to have a back end button in the plugin settings page that would disable all garbage collection all together for all the files on the server ?
– This way any super cache files or wp-cache files can only be deleted manually.
– I know there is already a back end option to manually delete the cache and I believe garbage collection only works when the cache expires by checking the cache timeout back end setting value.
Regards,
Omar M.> Is it possible to have a back end button in the plugin settings page that would disable all garbage collection all together for all the files on the server ?
Setting the GC timeout to 0 should do that, but even then there are times when cache files are deleted when pages or posts are updated.
When you edit a post type, or one of the plugins does, look for this text in the debug log:
“wp_cache_post_edit: Clearing cache for post”I created a test post type and edited it, and while I couldn’t force it to use ?x=y in the URL, editing it resulted in all cache files in / being deleted to refresh them. You might just be looking in the wrong place for the delete action?
-
This reply was modified 8 years, 7 months ago by
The topic ‘GC not working correctly !’ is closed to new replies.