W3TC cached pages expiring – setting?

  • Hi there,

    I’ve just started using W3TC so apologies for my inexperience first up.

    I’m primarily using the plugin for page and database caching. Once I’ve visited a few pages, everything runs really well for a while (a few hours) then I seem to have to cache the pages again. It’s like the cache expires. Looking into this a bit more, in the cache directory, I’m finding that the pages which have expired have the ‘.old’ suffix and as soon as I visit them again, this changes to ‘.html’ and everything is cached again for a while.

    Obviously I’ve got something set up wrong, I don’t want the cached pages to ever expire really as the site isn’t particularly busy. Can anyone advise me, is it something to do with cache preload or the purge policy?

    Many thanks
    Kevin

    https://www.ads-software.com/plugins/w3-total-cache/

Viewing 2 replies - 1 through 2 (of 2 total)

  • The pages will expire and therefore a new cahced version of the page is created. The old ones are cleaned up automatically by setting the garbage collection interval.

    Your pages are fine and the plugin JS running properly and there should not be any degradation in performance.

    Hi the_lar,

    Your site’s page cache may or may not regenerate depending on your site’s setup and W3TC configuration.

    The easiest way to always have a warm server side cache is to use the Warm Cache plugin. After installing, the plugin will attempt to detect the site’s sitemap. If it cannot, you’ll have to manually enter its URL.

    You will have to setup a cron job to crawl the sitemap and configure the cron job to crawl at the desired interval. If you don’t know how to setup a cron job, your host should be able to help you get one going.

    Best,
    AJ

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘W3TC cached pages expiring – setting?’ is closed to new replies.