Actually i am not too familiar with PHP code, but I try to figured out again by take a closer look on stopped upgrade step.
Some steps that I have tried:
-
Taking a look to Upgrade.inc.php file on line 1721, and i figured it out that this problem actually similar to this thread (i’m sorry not too deep search on this forum
). But i don’t see any matched solution for me from that thread. On my case, all journals listed on my existing OJS are also have Journal manager with role_id = 16 -
Look for an upgrade script that contains convertCommentsToEditor or similar word and i found 3.0.0_preupdate_commentsToEditor.xml on
~/ojs/classes/install/folder.
It seems that the xml file is trying to copy several columns on submissions table to a temporary submissions_tmp table, but i think it just stopped by the fatal errror produced during the upgrade process . cmiiw
-
Browse the submission_tmp table through phpmyadmin, and i found a submission_id = 328 with NULL value at date_submitted column.
I know that submissions_tmp table is just a temporary table during upgrade, so i can’t edit the value directly.
So i managed to find submission_id = 328 on submissions table, and filled out the submitted_time with the closest(estimated) time based on other row value.
-
I deleted the submissions_tmp table because later when the upgrade process is running, this table will be regenerated with new data.
-
Run the upgrade command from cli, and guess what, It WORKS!
I know it was a strange issue and i don’t have any idea with it, but at least this solution worked on my upgrade problem.
Thanks 