w3tc_flush_all does not immediately clear the cache

  • Resolved hedgehog90

    (@hedgehog90)


    2 years, 2 months ago

    I’ve had to implement a manual call to w3tc_flush_all whenever I update wp_options relating to my theme.
    However, for non-logged in users that are served a cached version of the site, it takes around 30 seconds for the changes to appear.
    This is with just page caching enabled.
    I assume that w3tc_flush_all is just queuing up a cron?
    How can I make it more immediate so the very next request is served a non-cached version of the site?

    Also, might it not be a good idea to add a setting so updated options trigger a cache clear?

Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @hedgehog90

    Thank you for reaching out and I am happy to assist you with this.
    w3tc_flush_all once called, is executed immediately. Depending on how you set up your manual call to w3tc_flush_all, it may take some time depending on the action that actually calls the flush.
    You can check this by manually purging the cache in the W3TC settings.
    As for the visibility, there is also a Browser Cache, so the cached page may take some time t to expire in the browser unless hard reloaded.
    In Performance>Page Cache>Purge policy, we have additional options where you can specify the pages and feeds to purge when posts are created, edited, or comments posted.

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘w3tc_flush_all does not immediately clear the cache’ is closed to new replies.