Serious issue with Database upgrade (failed from 3.2.1.3 to 3.3.0.2)

Software Support
15

Finally I successfully upgraded to 3.3.0.2.

For those following this thread my solution has been:

  1. ALTER TABLE submission_files ENGINE = InnoDB;
    due to all the tables need to use the same engine for being linked by a foreign key;

  2. Apply this patch: pkp/pkp-lib#6710 Unserialize journal settings depending on a value data type by Vitaliy-1 · Pull Request #6715 · pkp/pkp-lib · GitHub

Both before running the update.

Thanks to all.

5 Likes