Automatically prime the page cache not working

  • Hi all,

    I have a problem with Automatically prime the page cache option.

    If I purge all caches- _index_ssl.html file gets renamed to _index_ssl.html.old. The problem is that it never renames back to _index_ssl.html, unless I visit that page.

    As I understand- html pages should be automatically created in wp-content/cache with Automatically prime the page cache option enabled and time set?

    Thanks in advance for replies ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter RolandasZa

    (@rolandasza)

    Anyone? ??

    According to this post from 2011:

    W3 Total Cache relies on internal cron of WordPress and it’s only triggered by site activity. If your site has no visitors for a while loading the pages will be slower because: 1. W3TC will check if the current page is cache and if it’s expired. 2. Needs to clean up that expired page and re-generate a current copy. 3. Finally serve that file.

    It would be great if W3TC had an option to schedule a cache warmer cron job.

    I actually have a similar kind of issue… Our website uses varnish which when purging all caches loads the server too mush and produces 503 errors. So my questions is ,does the prime the page cache purges and recreates the entire cache or on demand when a specific page or resource is requested? Anyone knows?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Automatically prime the page cache not working’ is closed to new replies.