Describe the issue or problem
We upgraded from version OJS 3.3.0.19 to 3.5.0.5 and we noticed after the upgrade when looking over items that on the Journal Sections area that a second name now appears.
- Steps I took leading up to the issue
- We have a test environment for each of journals as well a production version. We upgraded the test environment
- We were testing internally and comparing the test environment (3.5.05) which is a copy of the production (3.3.0.19).
- We noticed that on the upgraded test environment on the Journal Sections area an extra name appeared.
- Also clicking on edit on one of the sections, only the second name is checked and not the 1st name.
Does anyone have any ideas that might have caused this to happen?
What application are you using?
3.5.0.5
Additional information
On 3.3.0.19 it has one name:
On the upgraded 3.5.0.5 there is an added name that appears:
Also, when clicking on edit on one of the above only the second name appears:
Hi @Stephen,
Hmmm… hard to say what is going on here. Is that additional section an orphaned section that was used previously? Are the articles assigned to that section?
-Roger
PKP Team
Hi @rcgillis It was just a copy of what is on production that was put on our test site. The test site was updated and has the extra names. I just checked and at least one of the sections was just used in the current Issue on the production site and on the test site. Did something change then from 3.3.0.19 to 3.5 that might have caused this? Thanks.
I can’t say for certain, as this looks a unique to your particular section setup.
If you were somehow able to check when that section was added that might provide some clues (might involve looking into the database, but may not be worth the effort.
Is it interfering with things on your end - affecting your use of OJS in anyway?
Also, I should note that version 3.5.0-6 is due to be released in the coming weeks, and that will provide some substantive improvements for the 3.5 release, so it might be worth waiting a bit to upgrade to that version.
-Roger
We host the journals so I am not sure at the moment if is effecting the use. We opened it up to our user to test and look over the test journals. Has the happened with other upgrades from 3.3.0.19 to 3.5.0.5? @asmecher