Fixed Hard refresh required on front end after disabling add-ons that modify CSS

[Jon W]

Not sure if this is new or only applicable to Chrome, but I've noticed that if an add-on has a template modification that extends a CSS file, disabling that add-on is not enough to remove that CSS and a hard-refresh is also required by the user.

Strangely, this only seems to affect the front end.

 

[Mike]

This is fixed now (for 1.4 and 1.5), thanks.