I, too, would like to see purging all caches change the minified filenames to help denote it’s a new version of that file (which the new page cache will use instead moving forward). Why not have some way of having the minified files be able to say it’s a new version?
My ideal setup would be to have the default W3TC browser cache expiration for CSS & JS files as well as having the CSS & JS minified. Now, I just need the ability to purge these caches to display updated JS/CSS code when needed. Otherwise, past visitors will potentially be using CSS/JS from weeks/months ago due to browser cache serving the old file since the minified filename didn’t change (even though the content did change).
Maybe the minified filenames periodically change as the page cache expires? I’m not sure, but currently I see using all of the features of W3TC in an optimal fashion leaves the minify feature with a bad bug.
Let me know if you hear anything about a workaround/fix/etc. or if it’s already accounted for within W3TC behind the scenes. Thanks!
I have also posted this at the similar topic at https://www.ads-software.com/support/topic/minification-and-cdn-minified-file-name-doesnt-change-when-its-content-does/#post-8863621
-
This reply was modified 7 years, 8 months ago by KZeni.