Question

Now that BugMonkey 2.0 is out, I started to use it of course. I split all our customizations into separate configurable ones. Great!

However... I noticed that for CSS changes in customizations to apply, I have to explicitly clear the browser cache. Even a 'hard' refresh using Ctrl+F5 is not enough. IIRC this was not a problem in the previous BugMonkey version.

I had this with IE as well as Chrome. For me it's not a big deal now that I'm aware of it, but for 'normal' users it is.

Edit: Probably because of this, after logging in (for example in an incognito window to test) I have to remember to always clear the cache and refresh. Otherwise the CSS customizations for logged in users don't load. :-S

Edit: To reproduce this:

1. start an up-to-date Chrome
2. go to FogBugz
3. enable a CSS customization that makes a clearly visible difference
4. clear all cookies and cache
5. go to FogBugz
6. log in
7. check whether the CSS customization works

For me it doesn't, until I clear the cache (not cookies!) again.

Answer 1

In short: if you're having to clear cache/hard refresh when you shouldn't need to, that's a bug, and we have a mechanism in place to fix it. I'll look into the issue you're having.

---

BugMonkey 2.0 does try to be better about caching; it won't regenerate your list of customizations unless it thinks that something has changed. (Whereas the previous version would send down your customization every time, adding overhead to every page request) I expect that after they're written, most customizations won't change very much, so the caching will make a lot of sense.

It should invalidate the cached version whenever you enable or disable a customization; if it isn't also invalidating when you're saving a customization that is applied to you, then that feels like a bug.

(One important use pattern is to be able to be editing or creating a customization, enabling it for yourself, "Apply"ing it, and being able to see the changes take effect in another window. This is useful for debugging purposes; if you aren't able to do this with just a soft refresh, then that would also be a bug)

So ... if you're ever facing situations where you're having to refresh or clear the cache etc, please continue to report them ... and we'll try to address those in a future release.