Section editors not shown after upgrading from 2.4.8 to 3.1.1-4

Software Support
1

Hi,
I have upgraded from 2.4.8 to 3.1.1-4
One of the things I see is that all those users that had the role Section Editor in 2.4.8 have lost this role in 3.1.1-4
I see in the 2.4.8 database that the table section_editors is empty. Don’t know if this has something to do with it.
Any idea?
Thanks in advance for your help
Regards,.
Juan

2

Hi,
Any help on this issue?
Maybe @asmecher can think of a solution?

When trying to select a section editor for a submission, no section editors are found.
Furthermore, as stated in my previous posts there are no section editors in my set of users after migrating to 3.1.1-4

Will I need to assing this role to those who were section editors in my old 2.4.8-1?
If so, will this action result in losing some activity history?

Thanks in advance.
Regards,
Juan

3

Hi,
Any help?
I’ve stopped my journal for some days now and will not like to extend the period many days more

Can anyone advice me on this issue?
Any help will be deeply appreciated!

Thanks in advance,
Juan

4

Hi @jascanio,

Users that had the section editor role in OJS 2.x should be given that role in OJS 3.x, regardless of whether they were listed as a section editor for a particular section or not (that’s the purpose of the section_editors table in both 2.x and 3.x).

Are you sure you’re working with a clean 2.x database, i.e. after an upgrade fails, have you dropped the database fully and reloaded from 2.x backup before running another upgrade?

Regards,
Alec Smecher
Public Knowledge Project Team

5

Hi @asmecher,
Thanks for your reply.
I’m affraid I’ve followed old upgrade guidelines. Not sure if I did what you say (I’ve done lots of things with the db. Had different collations in different tables of the database and some other issues)
I’ve had problems with languages, mail templates and more
Is there any tutorial or detailed guide or post in the forum where I could refer to?
Thanks in advance for your reply.
Regards,
Juan

6

Hi @jascanio,

The instructions in docs/UPGRADE or docs/UPGRADE.md (depending on your release of OJS) are considered the official reference. I’m afraid it’s hard to suggest specifics, but in general, the OJS 2.x to 3.x migration involves changing the way roles are represented. OJS 2.x uses the roles table, and OJS 3.x uses the user_groups / user_user_groups tables. The upgrade script should take care of migrating your section editors from one representation to the other (classes/install/Upgrade.inc.php in the migrateUserRoles function), but it seems as though that isn’t happening in your case.

Regards,
Alec Smecher
Public Knowledge Project Team

7

Hi @asmecher
Our starting scenario was as follows:

  • OJS 2.4.8 db with illegal mix of collations (solved with some queries)
  • Some submission files and folders lost a couple of years ago that could not be recovered due to lack of backups. Solved by adding dummy files

We had to upgrade from 2.4.8 to 3.0.2 which was more straightforward so the upgrade procedure could run. From 3.0.2 we then upgraded to 3.1.1-4

When upgrading, we found two main issues

  1. The absence of section editors, which I already mentioned

  2. And some review rounds with id null:

    9 [data: dbscripts/xml/upgrade/3.0.0_reviewer_files.xml]
    ERROR: Upgrade failed: DB: Column ‘review_round_id’ cannot be null

For the first main issue (1) we have assigned the role of section editors to those users who had that role in the 2.4.8 instance
¿Will this have side effects?

For the second issue (2) we don’t know exactly what to do and what is its reason.

Any idea?

Regards,
Juan

8

Hi @jascanio,

Fortunately, the cause of this was just discovered and fixed by another user – see No assignment for copyeditor/layout editor/proofreader after upgrade · Issue #4625 · pkp/pkp-lib · GitHub for details. The pull request attached to that issue (pkp/pkp-lib#4625 fix migration of stage assignments for copyeditors/layouteditors/proofreaders by ptrckb · Pull Request #2337 · pkp/ojs · GitHub) can be applied to OJS 3.1.1 and 3.1.2 (and possibly older versions too). You’ll need to apply it before running the upgrade script.

Thanks,
Alec Smecher
Public Knowledge Project Team

9

Hi @asmecher,
Do you mean the solution to issue 1) or issue 2) ?

Thanks
Regards,
Juan

10

Hi @jascanio,

That issue solves the original problem with Section Editor roles not being preserved in the upgrade from OJS 2.x to 3.x.

Regards,
Alec Smecher
Public Knowledge Project Team

11

Hi @asmecher,
ok, thanks for your reply.
Regards,
Juan