When I’m logged in as a user which is registered in one journal only the link refers to the site (!) homepage showing our general OJS homepage at www.biejournals.de. When I’m not logged in or when I’m logged in as a user which is registred in several journals the link refers to the respective journal homepage.
First of all, I think it should be the other way round. But why is here a difference at all? When I click on the journal’s logo I always want to get to the journal homepage, not sometimes to the site homepage. Or am I missing here something?
For the time being I just changed /lib/pkp/templates/frontend/components/header.tpl
Hi @bibliothekswelt, we have the same problem, we have 3.1.2-1 too, and I found that /lib/pkp/templates/frontend/components/header.tpl doesn’t change in 3.1.2-4.
We agree with you that
As far as I can tell this should be fixed in all 3.1.2+ versions. It’s possible that your theme has overwritten this template and the source of the problem may be there.
If not, feel free to add a link to the journal where this is happening and I’ll take a look.
Hi @NateWr, thanks for your reply.
The journal is Schermi. Storie e culture del cinema e dei media in Italia, I don’t know if theme has overwritten the template, we also have add some custom css.
Remember that the link is to site home only when a Schermi-only user is logged in.
Best regards
Stefano
Hmm, in that case I won’t be able to reproduce the problem by looking at the site. I’d recommend switching to the default theme to see if that fixes anything.
yes, our OJS 3.1.2-4 installation had this one in the code. BUT: With this code, any user other than an journal admin and who is logged in is relayed to the homepage of the multijournal site, not to the journals homepage, when clicking on the logo of the journal.
Hmm, I was able to reproduce this as a logged out user. If you can add additional reproduction steps to the issue for other cases that will be helpful.
We could not reproduce it for a public user (nobody logged in), but only for users that were logged in and did not have role journal admin (as I wrote above)