pages expiring on their own

  • Resolved Marios Alexandrou

    (@marios-alexandrou)


    11 months, 1 week ago

    I’m noticing that my cached pages are expiring within 3-4 hours. I’m determining this by looking at the folder and file dates of the cache folder. Where I’m expecting to see my site (5000 posts) mostly cached, I’m instead seeing folder dates that are at most 4-5 hours old and even in many of those folders the filenames contain “old” which I understand to mean they’re going to be clean out.

    I’ve tried having the Automatically Prime the Cache option on and off, but neither neither affects the age of the cached pages.

    My purge policy is to set to clear the Front Page, Post Page, and Blog Feed.

    I see 3 cache cleanup cron jobs set to run every 3600 seconds. And 1 pgcache prime cron job.

    There is at most 1 publish even per day. There’s quite a bit of spam commenting, but all comments are moderated so I’m assuming unapproved comments don’t trigger the purge policy.

    In a forum response 9 months ago, I read that “Since W3 Total Cache does not have cache expiry, meaning if the page is cached it will remain cached until the cache is purged manually or defined in the Performance>Page Cache>Purge policy.”

    What’s causing my cached pages to expire so quickly? What can I do if I want to prioritize caching even if it means content is occasionally stale?

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

    (@vmarko)

    Hello @marios-alexandrou

    Thank you for reaching out and I am happy to help!

    In some cases, some plugins or themes may call for the cache purge using the w3tc_flush_all(); hook.
    Can you please enable and check the purge log to see what may be calling these?

    Thanks!

    Thread Starter Marios Alexandrou

    (@marios-alexandrou)

    I searched all PHP files under /wp-content/ and there were 29 hits from 14 files for w3tc_flush_all, but all of the files are part of the W3 Total Cache plugin.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @marios-alexandrou

    Thank you for your information.
    This is why we need the purge log to see what has triggered the cache purge in that specific time period.
    Can you please check that?

    Thanks!

    Thread Starter Marios Alexandrou

    (@marios-alexandrou)

    The purge log is a pro i.e. paid for feature, isn’t it?

    SkyHiRider

    (@skyhirider)

    I am wondering the same thing, as my cache keeps getting reset and pages take too long to load, but getting the purge log requires the paid version.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @marios-alexandrou @skyhirider

    Yes, the Purge log is a Pro feature that can determine exactly when and what triggered the cache purge.
    You can try disabling the HTML&XML cache control and expires header and increase the garbage collection interval.

    Let me know if this helps!

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘pages expiring on their own’ is closed to new replies.