Support

Home Forums Custom Files Add-on (EE3) CSS versioning / caching best practice

CSS versioning / caching best practice

Posted: July 30, 2012 at 7:46 pm


Anonymous

July 30, 2012 at 7:46 pm

I recently ran into an issue where I updated some styling in /wp-content/uploads/espresso/templatesevent_espresso_style.css but the users of my site didn’t see the changes until at least a day later. I assume that’s due to typical browser caching of css and js files. That said when I “view source” of the affected pages, I can see that “?ver=3.4.1” is appended to the file path within the tag for the css file I changed.

My question is what’s the best practice for making sure that after making a change to css/js files I can force the browser to reload the changed resource? Is there a way to force an increment of the appended “ver” value? Also is this an Event Espresso or a WordPress feature?

Thanks in advance!


Josh

  • Support Staff

July 31, 2012 at 9:00 am

It’s a WordPress feature that can be overridden by using a plugin like this one: http://forrst.com/posts/Cache_busting_Path_Plugin_for_WordPress-esb

The support post ‘CSS versioning / caching best practice’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Do NOT follow this link or you will be banned from the site!
[i]
[i]