Multiple Custom Block issue on OCS 2.3.3.1

[JohnGrobler]

Good day,

We're running a new (non-upgraded) version of OCS 2.3.3.1. After adding more that one Custom Block instance on the /index.php/conf1/index/manager/plugin/generic/CustomBlockManagerPlugin/settings page and clicking save, still only one Custom Block instance is displayed on the Conference Style (step 4) page (/index.php/conf1/index/manager/setup/4). What actually happens is:

1) Custom Block A exist on Conference Style step 4.
2) I add Custom Block B on Custom Block Manager page.
3) When I return to Conference Style step 4, Custom Block A will be replaced by Custom Block B.

I've seen a similar issue reported for OJS here: http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=6076. The SQL command does however not work for OCS. After removing the non-existing columns form the SQL command and executing the query successfully (1 row added), the issue still remains. Please assist.

Thank you,
John Grobler

[jmacgreg]

Hi John,

I'll ask one of our devs to get back to you on this. In the meantime -- have you attempted to patch your system with the OCS diff listed in Comment #10 of that report (https://github.com/pkp/ocs/commit/47b55 ... 81a39.diff is a direct link to the diff file), subsequently followed by re-running the upgrade script? If you haven't, give it a shot, but make sure you back your db up first, of course.

I've also run into another problem, most likely entirely unrelated to yours, but I'll reference it anyway: see http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=6308.

Cheers,
James

[JohnGrobler]

Hi James,

Thank you for the feedback and link to the diff file. This is a new installation of OCS 2.3.3.1 (not upgraded). If I apply the patch to the inc and php files as described in the patch, should I run the DB upgrade script (staying on the same version of OCS) and will this script only upgrade database entries related to the custom block?

Thanks,
John Grobler

[jmacgreg]

Hi John,

Yes, that's correct. We've done a fair bit of work to ensure that the upgrade process is idempotent -- that is, you should be able to run it repeatedly, and only those things that change will be accounted for. That said, it's always good to have a fresh backup before you do so.

Cheers,
James