Describe the issue or problem
I’m facing error during upgrade OJS 3.4.0-5 to 3.4.0-6 using terminal command
Steps I took leading up to the issue
First, i check the version
$ php tools/upgrade.php check
Code version: 3.4.0.6
Database version: 3.4.0.5
Latest version: 3.4.0.6
Database version is older than code version
Run "tools/upgrade.php upgrade" to update
Then i try to upgrade using command below, but the error appear and upgrade process stopped right there:
OJS 3.4.0-5 and 3.4.0-6 are database compatible, so there’s actually no need to run the upgrade script when going between them. But I’ll ask someone to take a look into this.
Regards,
Alec Smecher
Public Knowledge Project Team
Now, the System Information page shows the current version number, also the update notification has gone away.
The version numbers shown are not sorted properly, but it just a cosmetic, at least it works like a charm right now
I tried the upgrade today, the same error occurred. Thank you @asmecher for the workaround, but the problem with the database still persist and we at our university are afraid that in the next upgrade the problem still persists, and may cause problems in a major version upgrade in the future. Thus, we yould like to know if there´s a precise explenation to why this error of the data format is occurring in the upgrade procedure. Please help and advise. Our cyber security team audits, oblige us to always have the latests code and data base versions.
Hi @joaoaires , if your current installation also use OJS 3.4.0.5, please give a try the method described by @asmecher .
It works on my case from 3.4.0.5 to 3.4.0.6. Just replace the old OJS code with the new one and add new record for 3.4.0.6 on versions table in order to remove the upgrade notification on siteadmin dashboard.
Hi @dnaite, i will try this method in my test environment … my only concern is that in future upgrades this problem will happen again and in the long term could be problematic in a major version upgrade.
I can 100% confirm that you are OK to update the code from 3.4.0-5 to 3.4.0-6 and not run the upgrade script. There is no need to update the versions table either, but you can do that if you like. Meanwhile, there will be feedback on the error message here soon.
Regards,
Alec Smecher
Public Knowledge Project Team
Hi all,
Unfortunately I cannot reproduce the problem, but maybe this change would solve the problem: pkp/pkp-lib#9813 cast int to string by bozana · Pull Request #4376 · pkp/ojs · GitHub.
I.e. converting/casting the $oldValue to a string (adding (string) in front of the $oldValue in that line).
Would anybody be able to test the upgrade with this change and report if it works then?
@bosana, your fix worked perfectly, thanks. I repeated the upgrade procedure from 3.4.0.5 to 3.4.0.6 and the upgrade script worked has expected. In both my test and production environments, I use a mysql (MariaDB) database.
