Logging out doesn't always allow full OPAC to load
Bug #1813673 reported by
Terran McCanna
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Low
|
Unassigned |
Bug Description
3.0.1 and 3.2.2:
Sometimes logging out of the web staff client doesn't convince the browser that you're logged out, so trying to go to the public OPAC interface doesn't load the header. It happens so sporadically that I haven't identified exactly what is happening, but my assumption is that there is a cookie that's not always being cleared upon logout, because clearing the cookies for the domain resolves the problem. (Of course, that also wipes out the registered workstations.)
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
importance: | Undecided → Low |
tags: |
added: opac usability removed: webstaffclient |
tags: | added: performance tt2 |
tags: | removed: tt2 |
To post a comment you must log in.
I see this semi-regularly too. We're on 3.2 currently.