Re: A cache-busting sledge-hammer

On Nov 9, 1:13 pm, Łukasz Rekucki wrote: > I would recommend using one of asset managers that provide JS/CSS > versioning instead. Their aren't very hard to install. You can compare > some of the more popular at > djangopackages.com:http://djangopackages.com/grids/g/asset-managers/ Seems like th

Re: A cache-busting sledge-hammer

I would recommend using one of asset managers that provide JS/CSS versioning instead. Their aren't very hard to install. You can compare some of the more popular at djangopackages.com: http://djangopackages.com/grids/g/asset-managers/ In most cases you get things like JS/CSS combining and compress

Re: A cache-busting sledge-hammer

That's a pretty neat idea, originally I was having to use { now|date:"u" } to put the current epoch timestamp on the end of the urls... On 09/11/2010 10:35, Ole Laursen wrote: Hi! If you have the problem of visitors getting errors from using the old Javascripts and CSS when you roll out a rele

A cache-busting sledge-hammer

Hi! If you have the problem of visitors getting errors from using the old Javascripts and CSS when you roll out a release, I have a sledge- hammer solution that only requires a single-line change in your settings.py. It's a middleware that examines the HTML from your views and appends a little ti