New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
What do you think of that "Cache busting/Versioning" method of Divi?
Does Divis approach to forcing the visitors cache to always update for new content make sense to you? Would you use it over regular expiry intervals or how do you handle this sorta issue?
Please take a second and read:
https://www.elegantthemes.com/blog/tips-tricks/how-to-use-versioning-to-update-your-cached-wordpress-content?utm_campaign=coschedule&utm_source=facebook_page&utm_medium=Elegant Themes&utm_content=How to Use Versioning to Update Your Cached WordPress Content
Comments
It is fairly standard.
We distribute large web applications (the standard is webpack for this), the generated files are named app.0a081bc8d2.js or whatever, and libraries are vendor.[hash].js, and this way the libraries don't update when we update application code - all caching can be done, doesn't matter, if there is an update the hash will change.
If we push an update that only changes comments.. the hash will not change (because it's generated post compile), so no cachebust, etc.
Manual file creation / upload is an old-style thing typically.