Hello Cedrick,
I think it would be very handy to have automatic “versioning” for css files in TC.
Problem: I regularly modify CSS rules or add code to e.g. the custom.css in templates made with TC. In order to apply the new rules I have at least to refresh a page or in a stubborn browser case, delete all the cache via a keyboard combination. That might be o.k. when preparing a site locally, but once in production, I can not expect every returning visitor to do the same and flush his cache when I change some rules. Because browsers nowadays rely heavily on cache, some will never get to see the results of a “changed” css. Furthermore, some “outside” cache systems can prevent to reflect changes.
As a solution I append “?and-some-things-like-a-number” to “custom.css” in the index.php file of the template after a change, but this is cumbersome, especially when you have to do it regularly in some cases. Although it works fine, it’s not practical.
I see others use versioning, why not TC?
Thanks for listening,
Jan
