• page caching begins only if you access all the pages on the site through the browser yourself, otherwise the cache is not created, after a while the cache is erased, without any action and is not created again

    • This topic was modified 7 months, 2 weeks ago by xisem.
Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @xisem

    Thank you for your review.
    You described how caching works out of the box, so I am not sure if you have had differen expectations for this and that is why your review is like this?

    By default, the page is cached when visted. And this page remains in the cache untill the cache is purged. This is how Page Caching works. In the W3 Total Cache, we also have the Cache Preload option in Performance>Page Cache, which can be used for the W3 Total cache to automatically preload all the pages in your website.
    Have you enabled this option by any chance?

    The Purge policy in the W3 Total Cache can be used to modify when and which pages will be purged from the cache. Meaning if the content is updated, the cache is purged to allow changes to take effect.
    This being said, some plugins like SEO plugins and even some themes are using the filters to call w3tc_flush_all(); so it means that the cache purge was called by another plugin or a theme.
    We would like to assist you with the configuration, however, as I can see you have not opened the support thread for this.
    This is not an issue or a problem, this is out-of-the-box behavior and this is how Page Caching works unless the Cache Preload is enabled.

    Let me know if you need assitance with the configration or if you have any questions about Page Caching.

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘does not cache, the cache is erased and not re-created’ is closed to new replies.