Currently doing test upgrade from 2.4.8 to 3.2.1-4 (3.3.0-6 direct upgrade failed)
Other than upgrade issue we want to report that in back end admin panel, not like the front end archived issue list where you can split the whole list by set value in “list” like 25 or 10 per page.
Backend back issue list by default loads EVERY issue! I have two large journals one with 5000+ issues published stucked forever (1+ hr past). Another one has less than 1000 took about 25 mins to load! the testing machine has 6 vCPU and 16Gb RAM tho.
Please do consider to add page split to back end too.
If this is already done in 3.3.0-6 please ignore my question.
Thank you for your post. I will bring it to the attention of our Dev Team to speak to some of the issues that you’ve noted. But please note that a direct upgrade path from OJS 2 to OJS 3.3 is not feasible. You upgrade to 3.2 first (as you are doing). This is outlined in the release notes for 3.3 here: OJS/OMP/OPS 3.3 Release Notebook - OJS/OMP/OPS