The discussion revolves around an issue where, when ‘strict logout’ is disabled, administrative actions (like pinning or closing topics) in new tabs remain accessible after logging out, even though they are ineffective. strager reports that logging out in one tab does not invalidate sessions in other tabs, leading to confusion as actions appear to succeed. sam initially finds the behavior odd, as the logout message appears across all tabs, but strager clarifies it’s specific to new tabs. sam suggests possible causes like browser plugins or long polling issues, while strager notes their instance has standard plugins and plans to test further. kensims identifies the root cause: the issue occurs only when ‘strict logout’ is unchecked, which sam confirms makes sense. The topic is reclassified to support for further investigation.
1.) Log in as an administrator
2.) Open a new tab to any post
3.) Return to the original tab and log out
4.) Return to the second tab and attempt to do things such as Pinning or closing the topic
5.) Observe the results
Actual Results:
Logging out does not prevent the administrative actions from appearing to occur in that tab. While these actions are ineffective (pinning a topic doesn’t actually pin it) it appears to the user that the changes are being made - this could lead to confusion if an admin logs out with one tab and returns at a later point to the tab where they are logged in - especially as you are able to change pages and still remain in this state.
Expected Results:
After logging out the sessions for other tabs should become invalid and any actions taken that a regular user cannot perform should result in an error.
Can you try a different browser? Can you confirm you don’t have any plugins? Does this happen on your home computer as well (perhaps you are shutting down long polling somehow)?
I have some late-night testing (DNS changes - what fun!) scheduled for tonight - I’ll try it again on my home system at that time and let you know.
We do have a few basic plugins installed, but they are pretty standard ones - new relic, sidebar, one or two others… it’s very possible that something with our instance is causing it. Leave this topic open (you guys can be a bit aggressive about closing them lol) for a day or two at least so I can get some more info