Issues from different journals mixed up in multi-journal installation (OJS 3.2.1.2)

We stumpled upon an issue with the issue-IDs in OJS 3.2.1.2, but this might be a problem for multi-journal installations in general.

You can access issues from other journals just by entering the issue ID as part of the URL. You don’t have to enter the correct journal ID.

Here are two examples from two different journals, both part of our multi-journal installation at biejournals.de:

Issue from InterDisciplines (InDi):
https://www.biejournals.de/index.php/indi/issue/view/107

Issue from JSSE:
https://www.biejournals.de/index.php/jsse/issue/view/276

If you enter
https://www.biejournals.de/index.php/indi/issue/view/276
you will get to the journal “Inter Disciplines” but you will see the issue from the JSSE!

The other way round is also possible (URL from JSSE, with Issue ID from InterDisciplines)
https://www.biejournals.de/index.php/jsse/issue/view/107

I think, this shouldn’t be possible and you should get an 404 error if you enter an ID that does not exist for this very journal, also the ID might exist in another journal.

We stumpled upon this problem because due to our migration all issue IDs have changed. In many cases the “old” issue IDs won’t work anymore because they don’t exist in the new multi-journal system, but in some cases the IDs still exist, but for another journal. You will now get to the correct journal, but you will see an issue from another journal.

Can this somehow be fixed?

Btw: The articles are NOT mixed up in this way - the IDs are separated and the IDs from one journal can’t be accessed via another journal’s URL. Here’s an example

Article from InDi:
https://www.biejournals.de/index.php/indi/article/view/1077

Article from JSSE:
https://www.biejournals.de/index.php/jsse/article/view/3467

Article with InDi-URL and JSSE-ID = 404
https://www.biejournals.de/index.php/indi/article/view/3467

Vice versa = 404
https://www.biejournals.de/index.php/jsse/article/view/1077

Hi @bibliothekswelt,

With apologies for the delay in responding – you’re absolutely right, there is a check missing!

I’ve filed this and added a fix here:

(Any of the linked commits will fix it; they are just applied to different branches.)

Regards,
Alec Smecher
Public Knowledge Project Team

1 Like

This topic was automatically closed after 2 days. New replies are no longer allowed.