I had restored the database but not filesystem.
I´m going to try again with a new backup od the database AND the 2.4.8 filesystem (I think you are talking about uploaded_files directory or I have to “restore” the ojs_3.0.2 sw toot?
No worries about git. For your purposes, you just want to restore the database and files_dir (the OJS software you can leave as-is), then follow these “command line” instructions instead of the web-based instructions at the end of the upgrade process:
Good news! I successfully update the OJS system to 3.0.2 (in a test environment).
There are many warnings that that I do not care about:
PHP Warning: Cannot use a scalar value as an array in /WWW/sp/ojs-3.0.2/lib/pkp/classes/core/DataObject.inc.php on line 133
PHP Warning: Cannot use a scalar value as an array in /WWW/sp/ojs-3.0.2/lib/pkp/classes/db/SettingsDAO.inc.php on line 41
but others worry me more:
WARNING: Unable to find a match for “690-938-1-PB.pdf” in “/WWW/ojs_uploaded_files/journals/2//articles/690/”. Skipping this file.
WARNING: Unable to find a match for “691-939-1-PB.pdf” in “/WWW/ojs_uploaded_files/journals/2//articles/691/”. Skipping this file.
I don’t know if it will be with the double slash before “articles” or what is the reason. If the problem is severe or what can be the cause?
The upgrade from OJS 2.x to OJS 3.x involves rearranging the contents of the files directory. The upgrade script goes through the files listed in the database, and renames/moves them on the filesystem. The message you’re getting says that a file was listed in the database but couldn’t be found in its expected location on the filesystem.
Public Knowledge Project Team
In your old, 2.4.8 DB table article_files, there is a column file_name. Those file names listed during the upgrade come from there, i.e. you should be able to find them in that DB table.
That warning/error means that the file is in the DB but not in the file_dir i.e. that there is a mismatch between DB and files folder. This mismatch could eventually happen by a not complete file upload or deletion or an earlier bug or… Thus, all those mismatches should be fixed before the upgrade – either the missing files should be deleted from the DB (maybe best from the Web-UI/ojs workflow) or uploaded to the files_dir (with the correct name and at the correct path).
The path of the files is file_dir/journals/<journalId>/articles/<articleId>/ and then further it depends: for example the public files (with ending -PB, as your example above) go to the folder public/, the submission files (with the ending -SM) go to the folder submission/original/, the copyedited files (with the ending -CE) go to the folder submission/copyedit/, etc.
Please do not forget to backup everything before the fixing and after the successful fixing, then use that clean backup to try a new upgrade.
I am trying upgrade ojs 2.4 to 3.0.2. I met too muct problems.
First, Duplicate entry ‘defaultthemeplugin-0-enabled’ for key ‘plugin_settings_pkey’
problem. I solved this problem by restoring my database from backup. After that
i faced with A database error has occurred: ALTER TABLE causes auto_increment resequencing, resulting in duplicate entry ‘2147483647’ for key ‘PRIMARY’ problem. also I have solved that problem by changing values of the tables on this DB.
later, I came across the problem of error 500. I corrected the error in php.ini file and this problem has been solved. bu now “405 not allowed /nginx” problem was appeared. Is there any one help me.