• I loaded the entire cache of my large site (nearly 15k pages all told), and then realized I had not set restart after completed. I did set up the cron job and confirmed it was working correctly to build the cache at 2-minute intervals.

    Now that the cache is full, I set “restart after completed”, the cron job runs, but no (or very few) new files are created – to see cache by date, I found this command:

    find . -type f -printf ‘%TY-%Tm-%Td\n’ | sort | uniq -c

    So I can see there are very few new files today, there should be thousands. I loaded from a web browser (and wget, just to see) and saw it confirm that new files were loaded, returning green ‘OK’, but the number of files cached today didn’t increase. It doesn’t return “Completed”, which is what I understand it would be returning if I hadn’t set the Reload after Completed option.

    I have a widget in the right-hand bar of the site that changes by week. So files cached Friday do need to be cached again today. It’s not a big deal if it takes 48 hours for all the files to be updated, but it doesn’t seem like it is updating at all.

    Is there something I have done wrong? Is the Reload After Completed seeing that the main content of that page is unchanged, and not redoing that page?

    While the cache was building, I definitely saw the number of older pages declining, even as it added new ones. But again it seems to have stopped, and I’m not sure what to do to force a reload other than deleting the cache entirely, which I had hoped not to have to do.

    Thanks!

Viewing 8 replies - 16 through 23 (of 23 total)
  • Thread Starter menken

    (@menken)

    We have changed Divi theme parameters, removed a social media plugin, and other things — and in all cases the full cache has been purged. The sassy-social-share plugin makes no mention of wpfc (nor does any of the themes in our themes directory), but when it was deactivated, the entire site cache was cleared.

    Is there any other process that might cause the wpfc cache to be purged, besides your delete feature?

    • This reply was modified 4 years, 1 month ago by menken.
    Plugin Author Emre Vona

    (@emrevona)

    you can disable both the “update post” and “new post” options of wp fastest cache.

    Thread Starter menken

    (@menken)

    I think we have to try update post — because maybe it thinks the post is updated.

    Plugin Author Emre Vona

    (@emrevona)

    which option did you choose on the wizard as below?
    https://www.wpfastestcache.com/tutorial/to-clear-cache-after-update/

    Thread Starter menken

    (@menken)

    It was set to clear post, page, categories — not the whole cache. But now it’s set to not clear at all, “Clear cache files when a post or page” is not checked, not for new and not for update…

    And… it still happened. I activated the “Sassy Social Share” plugin, and it immediately moved cache/all to tmpWpfc and started over. Even activating or deactivating the “Mammoth docx converter,” which doesn’t impact the front end, it just converts docx files to HTML in the wp-admin section, caused the whole cache to clear.

    I also noticed that it wasn’t updating even though “Restart after Completed” was checked, so something seems funny here.

    • This reply was modified 4 years, 1 month ago by menken.
    Plugin Author Emre Vona

    (@emrevona)

    if you disable both the “update post” and “new post” options, wp fastest cache does not clear all cache but a plugin may use our hook system and we cannot do anything about it.

    https://www.wpfastestcache.com/tutorial/delete-the-cache-by-calling-the-function/

    Is there no way to disable this system?

    I found that that was also my problem. I wanted to control the cache as manually as possible via FTP.

    Plugin Author Emre Vona

    (@emrevona)

    no, sorry. you can disable all the plugins to find out which plugin causes the issue.

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Preload Restart after Completed, only if needed?’ is closed to new replies.