[web2py] Re: Css cache problem

2014-01-24 Thread Alex
to answer my own question: for versioning specific files and not all css files I added the version text directly in the url: instead of response.files.append(URL('static','css/base.css')) I now write response.files.append(URL('static','_1.1.1/css/base.css')) this seems to work fine. Alex Am Fre

[web2py] Re: Css cache problem

2014-01-24 Thread LightDot
I saw your original message Don't know why it disappeared, though! I remember there were other similar reports (very seldom, mind you) a while ago, of messages disappearing or not even being posted to the group. I had this happen to me once, perhaps a year ago or so. AFAIK, just a glitch in

[web2py] Re: Css cache problem

2014-01-24 Thread Alex
cool, I didn't know about this feature! Currently I'm manually versioning my css files (renaming files). Is it possible to version only specific css files? Usually I'm only changing one or two files and I don't want all users to refetch all css files everytime I change one css file. regards, A

[web2py] Re: Css cache problem

2014-01-24 Thread Alex
cool, I didn't know about response.static_version. Currently I'm manually doing the versioning (renaming css file and adapting filename in response.files.append). Is it possible to apply response.static_version to specific css files? most of my css files never change and I don't want the brow

[web2py] Re: Css cache problem

2014-01-18 Thread LightDot
Hi and welcome! If you look at the source of the page in a browser, do you see the static_version inserted as a part of the path to your css? It should be something like /static/_1.1.4/css/somecssfile.css. After a change to 1.1.5, the path should change to /static/_1.1.5/css/somecssfile.css.