[MAGNOLIA-1554] 'Current user" indicator not refreshed after logging in to AdminCentral Created: 25/May/07  Updated: 19/Dec/16  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: zam6ak Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

If you let your AdminCentral session expire and then log in as a different user AdminCentral still shows previous user's id next to the logout link.



 Comments   
Comment by Magnolia International [ 25/May/07 ]

frame issue - the login screen should either "kill" frames, or the adminCentral page should.

Comment by Jan Haderka [ 05/Aug/09 ]

For now it could be easily fixed by using target="top" in the login form, but this attribute is (as well as whole frameset thing) deprecated in HTML 4.0.1 and not supported by xhtml-1.0-strict and loginForm.html currently declares to be strict xhtml "-//W3C//DTD XHTML 1.0 Strict//EN"

The whole issue will go away once we move on to new AdminCentral with GenUIne and abandon old framesets.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:28:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.