W3 total Cache and Asset Cleanup Cache Purge wipes all Cache

  • Resolved Dan14

    (@dan14)


    4 years ago

    I am using W3 total cache for css combine and minify and Asset cleanup for combine and minify JS. It works better like this for my setup.

    Asset cleanup has an option to cler css/js cache. When I do clear the css/js cache from assetclenup, not w3 total cache it wipes the entire cache including html.

    I have FSD with w3 total cache so everything gets wiped off the CDN. I did reach out to asset cleanup, they said that its possible w3 total cache have hooks that cause it.

    How do I stop the entire cache from being purged when assetclean css/js is cleared? I am assuming something can be done from your end.

    Assetclean up is a free plugin so you can test it under FSD setup, I dont know if it occurs without a CDN.

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

    (@vmarko)

    Hello @dan14

    Thank you for your inquiry and I am happy to assist you with this.
    This is expected behavior and let me explain why. You’ve set up the Full site delivery, and once the content on the website is changed, and taking into consideration the Purge policy in Performance>Page Cache, the cache is purged.
    Now I am not sure exactly how the mentioned plugin works, however as I explained, since the content of your website is changed, it also impacts the HTML and therefore the Cache is purged.
    I hope this helps!
    Thanks!

    Thread Starter Dan14

    (@dan14)

    All the plugin does is combine JS files. When one of the combined JS files is updated I will need to purge the JS files that are combined, is that correct? Same thing with combined CSS files on W3 total cache. If I purge only the minified files in W3 total cache that will not wipe the entire cache on the CDN including html and irrelevant JS an CSS files, is that correct? If yes, there is absolutely no reason purging only JS files that are combined will wipe everything from the CDN, like a full purge. It should only purge the combined JS files and that’s it. The developer of asset cleanup said that these are likely to be the hooks from W3 total. I would like to know how to fix this.

    • This reply was modified 4 years ago by Dan14.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @dan14

    Thank you for your patience.
    If there is a change to the CSS or JS file paths, then the HTML would change and therefore the cache would be purged to show the changes.
    We are still looking into this and I’ll get back to you on this.
    Thanks!

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @dan14

    Thank you for your patience.
    wp-admin/admin-post.php?action=assetcleanup_clear_assets_cache calls OptimizeCommon::clearCache()

    It deletes the cached files and directories not used. Once the files are deleted, new files are being created which of course are changing the content of the HTML, after that, the W3TC sees that page is updated, and given the options enabled in Performance>Page Cache>Purge Policy, the W3TC purges the cache.
    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘W3 total Cache and Asset Cleanup Cache Purge wipes all Cache’ is closed to new replies.