Upgrade from 2.4.8.5

[esciencepress]

Hi, four years back, I tried to upgrade my OJS 2.4.8.5 installation and a detailed comments on the issue are available in the closed ticket;

Issue in upgrading OJS 2.4 to OJS 3.x

Hi Team, I am facing this error while upgrading the OJS version from 2.4 to OJS 3.1. “Errors occurred during installation: A database error has occurred: Table ‘article_galleys_stats_migration’ already exists” I analyzed this error and I noticed that this error may occur because of the earlier upgrade process. But I did not do any upgrade to my website earlier. So please advice to fix this issue. Best regrads, -Calabe

I have learned MySQL structure of OJS 2.4.8.5 in detail and dropped the mix tables. Now, I assume that my database is cleaned and I tried to upgrade to OJS 3.1.2.4 however, my upgrade stopped at the following point with no error log;

[code: Installer Installer::provideSupplementaryFilesForReview]

When I change to

installed = on

The website, I believe, loads fine. However, the next upgrade to OJS 3.2.1.5 stopped at the following point;

Code version: 3.2.1.5
Database version: 2.4.8.5
Latest version: 3.4.0.8
Database version is older than code version
Run “tools/upgrade.php upgrade” to update
[user@server [installation folder]$ php tools/upgrade.php upgrade
[pre-install]
[load: upgrade.xml]
[version: 3.2.1.5]
[code: Installer Installer::checkPhpVersion]
[code: Installer Installer::syncSeriesAssocType]
[data: dbscripts/xml/upgrade/2.4.0_preupdate_usageStatistics.xml (skipped)]
[data: dbscripts/xml/upgrade/2.4.0_preupdate_usageStatistics2.xml (skipped)]
[code: Installer Installer::removeReviewEntries]
[user@server

[esciencepress]

DB Error: Duplicate entry '3-0-4' for key 'user_group_stage_pkey'

[user@host installation_directory]

[rcgillis]

Hi @esciencepress,

You may want to have a look at this post here: OJS 2.4.7 to 3.0.0 upgrade problems - #4 by knjigor

It seems like a similar issue.

-Roger
PKP Team

[esciencepress]

Hi @rcgillis and @asmecher

Thank you. Since, I compared database tables of my OJS2.4.8.5 with a fresh installation and deleted unnecessary tables which were mixed during a failed upgrade. Now, I changed lib/pkp/classes/security/UserGroupDAO.inc.php line 88 from…

return $this->getInsertId();

…to…

return $userGroup->getId();

and tried upgrading from OJS 2.4.8.5 to OJS 3.0.0. Thank you so much, Successfully upgraded to version 3.0.0.0 I am so happy as the database cleanup took years. I will further try to upgrade to the latest versions step by step.

[esciencepress]

Hi, I have been able to successfully upgrade to OJS 3.3.0.20 however, special characters on the text are not displaying correctly. I have gone through the post;

OJS 3 Special characters no longer show since upgrade from OJS2

We recently upgraded our OJS website ( thepolynesiansociety.org) website and the new webfonts available do not seem to support the extended font sets we need to display special language characters that are necessary. For example a with a macron (bar) over the top. I have set the basic template fonts e.g., Noto Sans etc and tried the others but none seem to put the macrons back (see latest issue page to see the problem). It is possible that I have to enable the extended latin subset fonts to s…

But no luck, please.

[esciencepress]

I reverted back and upgraded 2.8.5.0 to 3.0.0 = Successfull (with the following)
connection_charset = utf-8

Upgraded 3.0.0 to 3.1.2.4 = Successful (with the following changes:)

[solved] OJS upgrade OJS 3.1.2 to OJS 3.1.2.1, submission page HTTP error 500

Hi all I found this error. I use OJS Version 3.2.1.1. and Error log is: [02-Sep-2024 16:44:17 UTC] PHP Warning: assert(): assert($journal->getId() == $issue->getJournalId()) failed in /home/dscience/public_html/jurnal/classes/issue/IssueAction.inc.php on line 31 [02-Sep-2024 16:44:25 UTC] Slim Application Error: Type: Error Message: Call to a member function getData() on null File: /home/dscience/public_html/jurnal/lib/pkp/classes/submission/PKPSubmission.inc.php Line: 54 [image] It…

Upgraded 3.1.2.4 to 3.2.1.4 = Successful (with the following modifications)

SET default_storage_engine = ‘InnoDB’;

Tried to upgrade from 3.2.1.4 to 3.3.0.19 with the following;

‘engine’ => ‘InnoDB’,

The upgrade doesn’t proceed with

connection_charset = utf-8

It proceeds succussfully with

connection_charset = utf8

but characters show error for example (Côte d’Ivoire) appears (Côte d’Ivoire)

I tried to upgrade with connection_charset = utf8 and later changed connection_charset = utf-8 but website doesn’t load.