Logging out doesn't always allow full OPAC to load

[Terran McCanna]

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.)

[Anna Goben (agoben)]

I see this semi-regularly too. We're on 3.2 currently.

[Terran McCanna (tmccanna)]

Still a problem in 3.4.1

[John Amundson (jamundson)]

Evergreen 3.2.8

We are seeing the missing header not just after logging out, but while still logged into the staff client, as well.

For example, if the staff client resides at hostname/eg/staff and staff log in and then access hostname/eg/opac, the header will usually be missing. If it isn't, sometimes simply clicking to log in logs the user in automatically and removes the header.

We have an alternate url for our catalog, catalog.cwmars.org, that doesn't use the same hostname, that I suggest using for the OPAC if it's necessary to use it in the same browser profile in the staff client.

Using an alternate browser profile, incognito mode, or another browser also circumvents this issue.

[Terran McCanna (tmccanna)]

The missing header/footer while still logged in is related to this:

https://bugs.launchpad.net/evergreen/+bug/1538675

[Jason Stephenson (jstephenson)]

This is caused by a session cookie, if I am not mistaken. If you quit the browser, start it up again and then go to the OPAC without logging into the staff client. The OPAC works as expected.

[Terran McCanna (tmccanna)]

This is no longer an issue with the Bootstrap OPAC.