Tickets :: [#10156] Css is not updated

6.0.0-beta1

7/7/25

Summary	Css is not updated
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	goncalo.queiros (at) portugalmail (dot) net
Created	05/30/2011 (5152 days ago)
Due
Updated	06/04/2011 (5147 days ago)
Assigned
Resolved	06/01/2011 (5150 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

06/04/2011 07:30:47 PM	Michael Slusarz	Comment #5	Reply to this comment
Correct. The CSS cache's lifetime is controlled entirely by the lifetime configuration parameter. It is my understanding (Michael Slusarz can correct me if I am wrong), that this was done to save on many, expensive file stat calls on each page load for css files that are very unlikely to change. Yes, this was correct. The reasoning is that CSS will not be updated by anything else other than application updates. Javascript can potentially be updated by packages, so we can't rely on an application's version. I mentioned at the time I wrote this code that another css caching mode could be implemented (similar to JS caching), but I don't have the time/interest to add such a mode right now. In general, if playing around/developing with CSS (or even JS), caching should be entirely disabled.

06/02/2011 02:35:33 PM	Michael Rubinsky	Comment #4	Reply to this comment
Correct. The CSS cache's lifetime is controlled entirely by the lifetime configuration parameter. It is my understanding (Michael Slusarz can correct me if I am wrong), that this was done to save on many, expensive file stat calls on each page load for css files that are very unlikely to change.

06/02/2011 10:32:27 AM	goncalo (dot) queiros (at) portugalmail (dot) net	Comment #3	Reply to this comment
Yes css cache is enabled. So its not possible to change the css when cache is enabled without clearing css from cache? If javascript is cached it will still refresh its cache link if some js content is changed.

06/01/2011 07:38:36 PM	Michael Rubinsky	Comment #2 Assigned to Michael Rubinsky Priority ⇒ 1. Low State ⇒ Not A Bug	Reply to this comment
If css caching is enabled, this is the expected behavior. The themes cache is for caching things like the fs location of theme elements so the theme hierarchy doesn't need to be traversed each time.

05/30/2011 02:25:39 PM	goncalo (dot) queiros (at) portugalmail (dot) net	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ Css is not updated Queue ⇒ Horde Framework Packages Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
If we activate the css cache and change any css file, the changes won't be noticed until the app version is bumped, even if cachethemes is set to false.