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
{{ message }}
This repository has been archived by the owner on Feb 10, 2018. It is now read-only.
A common thing people do is pick up their badge and then immediately head over to tabletop to check out a game.
This year we've found that we often don't see their badge in the system for at least 15 minutes, even after refreshing the browser. I suspect there's some sort of caching issue; browsers often cache things even when the headers say not to, so our Ajax request that loads the users might not be getting re-called even when we say to. And I don't think we're even setting any of those no-cache headers anyway.
The text was updated successfully, but these errors were encountered:
More testing has revealed that a full page refresh does consistently fix the issue. This issue should therefore still remain, and the fix is that users shouldn't have to refresh their browsers to see new attendees. (There should be a periodic background update, but I guess that got broken at some point.)
however, nothing appears to ever call this, so the data is fetched once at page load and then never again. since this page is an angular app, it never actually refreshes, so, the data is stale until the user manually refreshes the page.
The solution here is likely to ensure that update() gets called. Eli seems to think this used to be on a timer or something, but looking through the history I couldn't find anything in this plugin, or in the original ubersystem repo before it was moved into a plugin, so it's also possible this was broken and we never really noticed much before.
-Dom
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A common thing people do is pick up their badge and then immediately head over to tabletop to check out a game.
This year we've found that we often don't see their badge in the system for at least 15 minutes, even after refreshing the browser. I suspect there's some sort of caching issue; browsers often cache things even when the headers say not to, so our Ajax request that loads the users might not be getting re-called even when we say to. And I don't think we're even setting any of those no-cache headers anyway.
The text was updated successfully, but these errors were encountered: