Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #74813


    one of my clients has the W3 Total Cache Pro version on a Woocommerce Shop.
    I have passed several hours of trying out and observing the caching behaviour but I am still not sure how it works in any detail – also not from your website articles. (Several other websites spreading also total nonsense…).
    Of course, we want to get out the most of your tool, but on the other hand make sure that no old content or prices are published…
    Could you maybe help us with the following:

    1) Is there a more detailed guide that explasin how to configure the caching for wocommerce?

    2) …same for common WordPress Websites?

    3) Concrete questions e.g.:
    a) How does the cache exactly work and how and when after an update of a page a new cached version is saved? – For example, I found out that Clearing the cache of a single page does not create a new cached version immediately…
    b) So, how does this depend on the settings of the cron job (number of pages to cache at once and time interval)?
    c) How exactly does the queue work?
    d) Sitemap entries also of relevance?

    4) As far as I found out (think so?) there is no option e.g. to clear and preload the cache of all pages e.g. at midnight for pages that do not need new versions more often? – I also had read that it should be possible and useful to set up a cron job at the provider… but all I could see in practice from the cache/page_enhanced folder, pages will always be rewritten based on other settings and non-stop over the whole day…

    Overall, a lot of information missing to understand how to configure the tool at it’s best and not by hazard.

    Could you help? Thanks a lot!



    Marko Vasiljevic

    Hello Thomas,

    Thank you for reaching out.
    The optimal W3 Total Cache configuration takes into account a number of factors: your theme, your plugins, and the technologies available on the server. Since everyone’s site, traffic, and theme are different, there is no one-size-fits-all solution.
    This is why there are no specific Guides for Woocomerce websites.
    1. This depends on what you are trying to achieve. Woocomerce is calling the W3TC hook to purge the cache once something is changed. It also has the option to fragment specific parts of the woo website using ajax to avoid these parts to be cached

    2. This depends on a lot of factors, however, Page Caching and Browser Caching are a good start.

    3.a) The page is cached once visited. After the cache is purged for any page or all pages, it needs to be visited again in order to be cached if not specifically configured to be Preloaded.
    b)c)d) In Performance>Page Cache, the re is a Cache Preload section. Once enabled and added the sitemap URL, upon the first visitation the W3TC starts to preload the entire website using the sitemap and by the Interval set in the Preload settings.
    4. No there is no setting for this specific use case as you mentioned, so you can for example create a custom cron to call the w3tc_flush_all(); and after that call the cache prime using wp-cli
    wp w3-total-cache pgcache_prime [–start=] [–limit=]

    I hope this helps and let me know if you have any other questions.


Viewing 2 posts - 1 through 2 (of 2 total)
  • The topic ‘Configure W3 Total Cache’ is closed to new replies.