openboxes / openboxes/openboxes
Resources (img, css, javascript) are not being refreshed from the cache after new releases
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 899
- Forks
- 503
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 54
Description
This is obvious, but we currently don't handle the case where resources are updated in a new deployment, but the browser cache holds onto an old version.
I think the resources plugin (asset pipeline in Grails 3) provides a mechanism for this, but not all css, img, javascript files are using the resources plugin. So we may need to add a request parameter (with app version as a value) to these links so they are refreshed automatically.
Temporary workaround:
Hard-refresh the page to refresh the web resources
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the asset pipeline and the CSS, image, and JavaScript links that bypass the resources plugin, then check how the app version is exposed during deployment. Done means resources from a new release are refreshed without requiring a browser hard refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100