You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The 3.4 release is doing a lot of cleanup operations on the database, but some entities were not fully handled intentionally. And due to the absence of a couple of foreign keys, new orphan data might reappear.
The remaining foreign keys will be covered by #8333.
As part of this issue, it's needed to:
Clear disk related assets: we cleared issue_galleys, submission_files, etc., but their related files remained alive both in the database and the disk.
Investigate whether we have other similar cases: independent entities that are considered orphaned when not linked to anything (e.g. the files table).
What application are you using?
OJS 3.4rc3
The text was updated successfully, but these errors were encountered:
Describe the bug
The 3.4 release is doing a lot of cleanup operations on the database, but some entities were not fully handled intentionally. And due to the absence of a couple of foreign keys, new orphan data might reappear.
The remaining foreign keys will be covered by #8333.
As part of this issue, it's needed to:
issue_galleys
,submission_files
, etc., but their relatedfiles
remained alive both in the database and the disk.files
table).What application are you using?
OJS 3.4rc3
The text was updated successfully, but these errors were encountered: