[Resolved] [OJS 2.4.8] Reviewing interest lost after upgrading from 2.3.3 to 2.4.8

After upgrading from 2.3.3 to 2.4.8, editors can search reviewing interest while assigning reviewers and the reviewing interest field is empty when viewing user information.

I checked the database table user_settings and found the interest values are still there. One table named “User_interest” was added in 2.4.8. I had an issue (duplicate entries) during the upgrade. I deleted a few entries and upgraded successfully. Are these two tables related in some ways?

Thank you.

Paul

Hi @Paul_Chen,

The details of this upgrade process are pretty foggy, as it’s quite old – but the details will depend on which release of OJS 2.3.3 you were using (2.3.3-0, 2.3.3-1, 2.3.3-2, or 2.3.3-3). There are two relevant functions in classes/install/Upgrade.inc.php (migrateReviewingInterests and migrateReviewingInterests2) that get run along the way from 2.3.x to 2.4.x, and the first is only required for early builds of 2.3.3.

Regards,
Alec Smecher
Public Knowledge Project Team

@asmecher,

Thanks for the response. It is 2.3.3.0. I think I upgraded it successfully. As I mentioned, the values for reviewing interest are in the user_settings table of 2.4.8 but the are not pulled/shown in the user details and reviewer selection pages in 2.4.8. The user_interest table in 2.4.8 has only two columns: user ID and controlled_vocab_entry_id. What is controlled_vocab_entry_id? Does this user_interest table have anything to do with reviewing interest?

Thank you.

Paul

@asmecher,

I checked the related DB tables in both versions (controlled_vocabs, controlled_vocab_entries, controlled_vocab_entries_settings, user_interests). After upgrading, the controlled_vocab_entry_id in user_interests does not seem to correspond to the setting_values in controlled_vocab_entry_settings with the same controlled_vocab_entry_id. It looks like the setting_name and setting_values in user_settings are not used. Since I don’t want to redo the upgrade of entire database, how can I just work with these tables: controlled_vocabs, controlled_vocab_entries, controlled_vocab_entries_settings, user_interests to make it work? A simple script from the upgrade class?

Thank you very much.

Paul

@asmecher,

I figured out the problem. The database was messed up during the many upgrading attempts. I copied the “good” tables from one database to the current database. Problem solved.

Thank you.

Paul

1 Like