I’m a little fuzzy on why it happens.  But I just tried manually adding the links with no globals used and no v. number added and it worked fine that way.  Wouldn’t use it for a production site- but for developing, would that work?

Chris Jennings - 24 January 2008 06:48 AM

During the development cycle this feature is a nuisance! I tend to use CODA now to edit templates from saved copies out of the EE templates. I find that editing the CSS outside of EE - the fresh CSS isn’t getting picked up and I have to go back into EE and edit in the template. Yes I know I could edit the CSS quite separately, but this causes a problem having a CSS outside of the templates.

I guess what I am asking here is - can this feature be turned off as an option somewhere?

It’s only triggered by use of the {stylesheet} path variable.

Thanks Derek,

I had noticed this the other day and knew that it must be something that was built in to EE so looked through the change-logs and found it listed there. I only noticed it as I had just installed a new Dev install to test something out and I just left the standard template in there and this is when I saw it. I have another site running 1.6.1 but I never use the {stylesheet} path variable so figured out what was going on. I recognised the numbers immediately as I used to do this sort of thing in Flash many moons ago to refresh content. An old trick but always a good one!

So the answer is that you can over-ride this by simply not using the {stylesheet} path variable although I may try using it from now on as it really is a neat feature!

Best wishes,

Mark

Yeah, I might start keeping my CSS in EE now because of this feature. Especially now that CSSEdit recognizes a CSS file even when it has a .php extension.