Timeline for How to force flush CSS cache on client side?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 20, 2019 at 13:59 | comment | added | Arslan Tabassum | this should be improved..... | |
| May 31, 2016 at 19:16 | comment | added | Mark Shust at M.academy | this is a horribly unproductive solution to this problem | |
| Apr 13, 2015 at 6:17 | comment | added | Duke | Don't even think like that! | |
| Aug 26, 2014 at 10:23 | comment | added | Marius♦ | I don't know how you do deployments, but this way I have to keep the old theme folder until I change the value for package/theme, or create a script that updates the value on install. Also, if I have different themes set for different periods of time they might be affected. Duplicating a lot of files is bot the easiest way by far. For example installing this: github.com/jreinke/magento-suffix-static-files is much easier. All you have to do is go an change a number in the backend after each deployment. | |
| Aug 25, 2014 at 22:00 | comment | added | Fabian Blechschmidt | If something goes wrong, you roll back, which should include another (the old) filename, therefore changing the configuration (read as package/theme) is not needed | |
| Aug 25, 2014 at 21:27 | comment | added | The Phil Lee | Why not? This way if something goes wrong with the new version, you can quickly go back to the old version. If you are using long browser-caching times and/or CDNs to serve your css (and js which might also need to be flushed/invalidated), this is by far the easiest way. | |
| Aug 25, 2014 at 20:58 | review | Late answers | |||
| Aug 25, 2014 at 22:00 | |||||
| Aug 25, 2014 at 20:43 | comment | added | Marius♦ | no, you never do that. that's really a bad way of doing it | |
| Aug 25, 2014 at 20:40 | history | answered | The Phil Lee | CC BY-SA 3.0 |