In OJS dashboard the username is not shown in the upper right corner (image 1) neither right of the user circle icon nor in the dropdown menu.
Again in the OJS dashboard (image 2) when the main user (admin) logs in as another user (anotheruser) the username is not shown in the upper right corner but the a new little user circle icon appears and in the dropdown menu there is a message telling you that you are logged in as “anotheruser”. This message doesn’t show the username “admin” but shows an uninitialized varialbe {$username}
In the journal view the “admin” username (image 3) and the “anotheruser” (image 4) are shown.
We are using OJS version 3.3.0-8.
I’m not sure wheter this is a bug or it must be requested as a new feature. I’ve posted it as an issue in github
In a screenshot on the OJS Documentation one can see in upper right corner a username “dbarnes” shown (image 5)
A, OK, now I got it. As I understand that has been changed and the username is not available there anymore. Unfortunately, I have no idea how to implement it to get it there again, sorry. Maybe some developers can give you a hint.
But the username is obviously generated to the UI under div.pkpDropdown.app__headerAction.app__userNav button.pkpButton span.-screenReader which in turn is positioned 2000px to the left of the user circle icon via css:
I very much second this request (already upvoted). As site and journal manager with several identities of different granularity of access rights, it is very annoying that I cannot see with one glance which identity I am currently using but only find out when I am not allowed to do certain things.
Create a directory chrome in your firefox profile directory (in Windows usually C:\Users\username\AppData\Roaming\Mozilla\Firefox\Profiles\#####). You can see the actual profile directory via about:support in Firefox.
Create a file userContent.css in the new created chrome directory with following content (don’t forget to replace “www.example.org” with your domain!):
We are trying to make all first “Feature Request” posts follow the same structure. We hope this will make it easier to understand the requests and, at the same time, ensure that no relevant information is missing.
Could you please edit your post following this template?
Describe the problem you would like to solve
Example: Our editors need a way to […]
Describe the solution you’d like
Tell us how you would like this problem to be solved.
Who is asking for this feature?
Tell us what kind of users are requesting this feature. Example: Journal Editors, Journal Administrators, Technical Support, Authors, Reviewers, etc.
Additional information
Add any other information or screenshots about the feature request here.