@diosmosis opened this Issue on October 13th 2014 Member

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.

@gaumondp commented on October 14th 2014

IMHO , also related to #6402.

@mattab commented on October 17th 2014 Owner

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?

@diosmosis commented on October 17th 2014 Member

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.

@mattab commented on November 3rd 2014 Owner

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.

Ok so maybe this is rather a browser bug? Hopefully it will be fixed sometimes!

@diosmosis commented on November 3rd 2014 Member

Looks like a browser bug, no issue w/ firefox.

This Issue was closed on December 1st 2014
Powered by GitHub Issue Mirror