Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: WebApp version isn't always updated on server upgrades #690

Closed
chenilim opened this issue Jul 8, 2021 · 1 comment · Fixed by #755
Closed

Bug: WebApp version isn't always updated on server upgrades #690

chenilim opened this issue Jul 8, 2021 · 1 comment · Fixed by #755
Assignees
Labels
Bug Something isn't working

Comments

@chenilim
Copy link
Member

chenilim commented Jul 8, 2021

Steps to reproduce the behavior:

  1. Install Focalboard plugin v0.7.0
  2. Open the Focalboard workspace
  3. Note the displayed version (should be 0.7.0)
  4. Remove the plugin from the server
  5. Install Focalboard plugin v0.7.3 (or another different version), via custom plugins on the server
  6. Close and reopen the Focalboard workspace
  7. Note the version number - in some cases this is still 0.7.0

A force-reload of the browser will update the webapp to the latest version

Expected behavior:
The webapp always shows the currently installed version.

Platform:

  • Chrome 91 on macOS 11.4

Additional context:
It appears that the browser caches the old version of the webapp. We may need code changes to force it to load the latest version, e.g. by appending a guid / timestamp to the webapp file names.

@chenilim chenilim added the Bug Something isn't working label Jul 8, 2021
@chenilim
Copy link
Member Author

chenilim commented Jul 8, 2021

@sbishel, I think this one is worth investigating and fixing earlier, before we get many more upgrade scenarios out there. Please reassign as needed. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants