You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
diosmosis opened this issue
Oct 13, 2014
· 5 comments
Labels
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
If a plugin is activated, the JS & CSS will be re-aggregated and merged, but the browser won't try to issue a request for the new merged assets since it will still have a cached version. Somehow the browser cache needs to be reset after a plugin is activated.
The text was updated successfully, but these errors were encountered:
If a plugin is activated, the JS & CSS will be re-aggregated and merged, but the browser won't try to issue a request for the new merged assets since it will still have a cached version. Somehow the browser cache needs to be reset after a plugin is activated.
Are you sure that this works this way? IIRC when disabling plugin it should invalidate the getNonCoreJs cache in the browser by regenerating a new cb cache buster value?
Looks like there's a new cache buster, however, on chrome it doesn't result in the new script being loaded until I reload the page. I haven't looked into the issue that much, though.
BugFor errors / faults / flaws / inconsistencies etc.wontfixIf you can reproduce this issue, please reopen the issue or create a new one describing it.
If a plugin is activated, the JS & CSS will be re-aggregated and merged, but the browser won't try to issue a request for the new merged assets since it will still have a cached version. Somehow the browser cache needs to be reset after a plugin is activated.
The text was updated successfully, but these errors were encountered: