Cache busters and injectScript and friends

[anthonyryan1]

What would you like changed about the web client?

On each release, you've been updating the cache busters on all the scripts in index.html

This is not currently applying to injectScript, and I saw quite a few people having problems during the migration from 5.1.x to 5.2.x because their browser was serving up-to-date files from /js/*.js but the plugins were still cached to 5.1.x.

Describe the solution you'd like and propose possible alternatives.

Should we add cache busters to injectScript() and injectCSS() so they'll change with each version bump?

Or should cache management be considered part of of the web server config with etags/last-modified. And stop relying on a cache buster. We could handle this by documenting recommended web-server configs for popular web servers.

Right now, we're cache-busting the most important files, but anyone using plugins can still have plugin breakage across releases. So it would be nice to get a a more application-wide solution.

Provide information and resources about the environment hosting the web client.

Firefox 139 & Chrome 137 PHP 8.3.22 Gentoo Linux Install script

Additional context

No response

[stickz]

Thanks @anthonyryan1 for this issue report. The recommended solution is to use cache busters with each version bump. There are many reasons why it's better to control this at the application level instead of the web server.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[anthonyryan1]

Keepalive.

I will make a PR for this when development resumes.