Hello,
I am working on upgrading multiple OJS stable-3.2 to lts-3.3, and I am finding that in the upgrade process I am getting complaints like this:
2024-06-14 17:18:02 [migration: PKPv3_3_0UpgradeMigration]
Removing orphaned submission_files entry ID 1362 with submission_id 654
Removing orphaned submission_files entry ID 3975 with submission_id 1111
Removing orphaned submission_files entry ID 5433 with submission_id 1362
Removing orphaned submission_files entry ID 5459 with submission_id 1368
Removing orphaned submission_files entry ID 5460 with submission_id 1368
...
Before going on, I would like to get a good understanding of why this might happen and the long term implications.
From the message, I guess that OJS is trying to maintain the integrity of the DB by removing references to files that it does not find on disk (in other words, the DB and the file system are not synchronized).
Funny part, it’s not just the missing file, it’s that most of the items listed no longer exist in the DB… that is kind of wired.
So, I wonder if any or all of these reasons can justify entries of this type:
- Delete article’s feature: older versions of OJS allowed the deletion of articles. It left this function undefined references.
- Disk recovery: The provider where we have the server has the DB and the disk in different storages. The error may be due to a recovery of a previous snapshot of files without recovering the DB.
- Connectivity problems: Connection failure (either on client or server) during the upload of a file.
- Previous problem: Most of them are OJS that come from version 2.x. Could it be that these are previous integrity errors that 3.3 now detects and surfaces?
- Virus or backup issue: Although here it’s not the case in forum fellows report issues with backup sync or virus where files were removed.
- Others: Is there any other reason for this?
About the long term impact, I can imagine the answer but I prefer your expert opinion.
Obviously, if the file does not exist, OJS is not going to be able to invent it… so by removing the reference, it will be as if it never existed, no?
Final question… I have been searching through different backups and have located some of the remaining files (some in v2, others in v3 filename format). I understand that if I add the file and its name follows the v3 syntax it will find it and the error will disappear (?) but if it is in v2, it will not be able to retrieve it.
So the question is: Is there an easy way to rename files from v2 to v3 without doing the upgrade again? If not, is there any equivalence table to convert the names (e.g. CM is 1-9, the date is the creation date…) to create an script to do the job?
Thanks for your time!
Related posts
