Updating to a new Piwik version should automatically force the browser to update the cache for JS/CSS files
|Reported by:||matt||Owned by:|
Description (last modified by matt)
This issue has always existed in Piwik, after each upgrade where some JS or CSS were updated, some users would experience issues as their browser would still use the old cached JS or CSS and this would break some bits of Piwik. This became a more important issue with 0.2.35 where a lot of the JS files were updated and broke the dashboard for most users; to fix it they had to find out the issue (eg. looking at the forum) and delete their browser cache, which is not a good user experience.
There are several ways we could fix this:
- Quick fix: route all JS/CSS inclusions through a common mechanism (smarty function or similar) and automatically add a parameter jquery.js?piwik=0.2.35 to force the browser to refresh all the cache after each upgrade
- Ideal solution: a better solution would be to route all JS/CSS inclusions requests through a simple merge + minify script which would: make Piwik faster (only one http request for all inclusions, and return smaller minified content) and fix this issue (we would add the &piwik=0.2.35 parameter to this merge script). See solution described in #660
If anybody wants to help please shout! This feature is def a good one for a developer new to the project.
Change History (12)
comment:10 Changed 5 years ago by vipsoft (robocoder)
- Resolution set to fixed
- Status changed from new to closed
comment:11 Changed 5 years ago by vipsoft (robocoder)
- Milestone changed from 2- DigitalVibes to 1 - Piwik 0.4