Cache not clearing – problem has returned

  • Resolved jason9j

    (@jason9j)


    3 years ago

    Hi – please see my updates to this existing topic:

    https://www.ads-software.com/support/topic/very-basic-question-purge-for-existing-visitor/

    The topic was previously marked as resolved, which must be why there has been no response to my recent update.

    The problem has returned.

    Browser needs to be hard refreshed to see changes, despite purging all with the plugin. This creates issues for return visitors. Can you please let me know why the issue persists and how to fix it so I can keep using this plugin? Much appreciated.

    I have disabled the plugin and cannot use it until it purges properly without the need for a hard refresh (most visitors will never do that).

    Here is an updated report number: EYTMIBAD.

    Please let me know ASAP. Thanks.

Viewing 5 replies - 1 through 5 (of 5 total)
  • tenkstars

    (@tenkstars)

    Hi,

    Please try disabling “Browser Cache” and see if it’ll fix the issue.

    Regards.

    Thread Starter jason9j

    (@jason9j)

    Thanks. I’ll try it and let you know. However, will ‘Purge All’ still instantly purge everything in returning visitor browsers? After I ‘Purge All’, I just need it to cause all files to be downloaded again, fresh, the next time they visit the page. Will the plugin do/trigger this? I don’t want it bypassed handed over to the server TTL settings….

    tenkstars

    (@tenkstars)

    I maybe be wrong but my understanding of how the “Browser Cache” feature works is that it tells the browser of the visitor’s device to cache the static files such as CSS, JS, images, and videos of the webpage, but the LSCache plugin’s purge actions won’t reach out to the visitor’s browser to clear the cache. The default TTL of the browser cache is 1 year.

    Thread Starter jason9j

    (@jason9j)

    Thanks for your reply. Basically, when I make style changes (i.e. CSS), I simply want to purge all the old styling and replace it with the new, so that next time a person visits the site, the new styling is downloaded. I don’t want them to have old CSS rules from their browser applied to new structures, as this messes up the page. I thought that the point of ‘Purge All’ is to ensure that visitors download the new, correct files when they next load the page, because the purge is telling their browser to download it all again…?

    Currently, I can ‘purge all’ all I want, but I don’t see changes until I do a hard refresh (Ctrl + F5), which of course no visitor is going to do, and even I don’t know how to do a hard refresh on a mobile browser.

    If ‘purge all’ doesn’t cause new files to be downloaded upon next visit, what is the point of it? I’d really appreciate a better understanding. Last time I raised this issue, a technical issue was acknowledged. I figured that it has simply returned with a recent update…..I just want users to download new files after I have made changes.

    Any guidance is appreciated.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Did you see the CSS file name changed ? after you edited the original CSS files and purged all ?

    Best regards,

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Cache not clearing – problem has returned’ is closed to new replies.