Hi @wegwarte –
What are your garbage collection settings? I am wondering if the two are conflicting.
The garbage collection was deactivated (0 seconds). And in the garbage collection section of the settings, there was a warning that supercache files aren’t removed because preload is activated.
Meanwhile I’m using a bash script to rebuild the cache files for all posts automatically every hour (iterating through the post URLs from the sitemap.xml and calling wget on each URL).
Hi there,
I’m honestly not sure why that’s happening. It could be that the preloading process is encountering an error while trying to access the pages. This could be due to a temporary issue with the site or the server.
It could also be that the cache directories are being deleted by another process or plugin. Some other plugin or process on your website could be removing the cache files.
Note that unless your site is particularly slow, preloading shouldn’t be necessary as visits to the site will naturally result in caches of those most visited parts of the site.
Well, maybe it’s a server issue, but I didn’t see this problem with an other cache plugin. When the issue occured, no other cache plugin was installed which could have interfered with WP Super Cache.
I need a preloaded cache because my site is really slow. Without cached pages, loading a page took 5 seconds sometimes; with cache (static HTML files) only fractions of a second. Maybe this was the reason my site wasn’t found by Google, while another site without WordPress & PHP & DB on the same server is well indexed, even without any special SEO.
-
This reply was modified 2 years, 11 months ago by
Wegwarte.
Hi @wegwarte
Have you by chance disabled wp-cron? Sometimes sites recommend doing this as a way to get better performance out of a server, but doing so would mess with WP Super Cache.
The other possibility is an issue that we’re looking into here:
https://github.com/Automattic/jetpack/pull/28545
A patch is being prepared for the issue described there, which seems similiar to what you are experiencing.
I haven’t disabled wp-cron by inserting “define(‘DISABLE_WP_CRON’, true);” into the wp-config.php file, but since my site doesn’t have many visits, and my server doesn’t provide cron jobs, I set up a cron job on a local Raspberry Pi to trigger wp-cron every minute:
* * * * * wget -O- https://mydomain.com/wp-cron.php > /dev/null
If you haven’t disabled wp-cron, then it’s likely the issue that Bruce linked to above may be causing this. That should hopefully be fixed in v1.9.3, so let’s see if that helps.
Hi @wegwarte – we’ve just released Super Cache 1.9.3, which includes a fix for what I believe is the underlying cause of the issue you’re having.
Please try updating to 1.9.3, then visit the “Preload” page in your Super Cache settings. Click “Save Settings”. Just hitting that button should double-check your cron-job is set up.
Please let us know if that solves the issue for you – or if it continues.
