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.

Sign up for GitHub

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

Jump to bottom

Should recook javascript registry #13

Open
gaudenz opened this issue Jul 4, 2013 · 0 comments
Open

Should recook javascript registry #13

gaudenz opened this issue Jul 4, 2013 · 0 comments

Comments

@gaudenz
Copy link
Contributor

gaudenz commented Jul 4, 2013

At least version 1.0.6 and 1.0.7 include changes to the contenttree.js file registered in the javascript registry without an upgrade step to recook the registry. Without recooking the registry clients may still cache the old version for up to 1 year (!).

Is it expected that users detect these changes themselves and recook the registry? IMO all changes to registered resources should have an associated upgrade step.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gaudenz