• Resolved swagatam1975

    (@swagatam1975)


    Hello Team,

    Thank you for this wonderful cache plugin, it works great, however I have one serious concern.

    Despite of having all the purge rules set for expiring after 30 days, my page cache keeps refreshing every two days.

    My domain name is: homemade-circuits . com

    I am using W3TC only for page cache, Redis object cache, browser cache, that’s all.

    My page cache purge rules are set in the following manner:

    Automatically prime the page cache:

    Update interval: 5 seconds

    Pages per interval: 10

    Purge Policy: Page Cache:

    All Fields Disabled, except the “Post comments pages” which is Enabled.

    Advanced

    Maximum lifetime of cache objects: 2592000 seconds

    Garbage collection interval: 2629800 seconds

    Comment cookie lifetime: 1800 seconds

    I would really like the cache expire time to follow the above TTL rules, and not abruptly purge within two days.

    Any suggestions to solve this problem will be greatly appreciated.

    Thank you for your time!

    Swag

    • This topic was modified 3 months, 2 weeks ago by swagatam1975.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @swagatam1975

    Thank you for reaching out and I am happy to help!
    I’ve checked yoru website and I can see that you are using another caching solution besides the W3 Total Cache? Can you confirm this and please let me know if you added this before of after you created this topic?
    Also, please let me know how you determined tht the cache is purged every 2 days? Have you checked the purge log and see what triggered the purge?

    Thanks!

    Thread Starter swagatam1975

    (@swagatam1975)

    Thank you @vmarko, for your kind reply!

    Yes, I am using the litespeed cache plugin from beginning along with W3TC, but I am using the litespeed plugin only for page optimizations, not for caching.

    All the caching options for litespeed are completely disabled.

    I am using it only for ,CSS, JS, and HTML optimizations, and nothing else.

    For caching I am using only the W3TC plugin.

    To check the page caching behavior, first I open a specific post in incognito mode, so that it gets cached by W3TC.

    Then I edit the post by altering a particular word in the post and update the post.

    Then I go back to incognito mode and open the same post again, and I find that it is not showing the updated version of the post, which means the caching is working. Then I confirm this by refreshing the post many times, and find that it is showing the cached version only, and not the updated version.

    Then I keep track of the post by checking the post from time to time in incognito mode.

    For a couple of days I find the post not reflecting the updated version, but then suddenly I find the post showing the updated version without any kind of manual purging being triggered. No plugins updated, no comments posted yet the page is randomly purged after maybe around two days.

    So this is how I check the caching behavior of the plugin.

    please let me know if there’s any further information you need from me.

    Awaiting your kind response!

    Swag.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @swagatam1975

    Thank you for the clarification.
    This means that something else may be calling the purge or w3tc_flush_all(); like some other plugin or theme.
    If the settins are as you mentioned, there is nothing in the W3 Total Cache that will call the purge, and you can check the code to confirm.
    This is why I asked you to check the Purge log in Performance>General Settings>Debug section. This will give the answers on what is purged and what called the purge.
    I hope this helps!

    Thanks!

    Thread Starter swagatam1975

    (@swagatam1975)

    Thanks very much for the clarification!

    I will check it from my end, and let you know soon.

    Best Regards

    Swag

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.