PKP Bugzilla – Bug 6667
Upgrade does not mark old version as no longer current
Last modified: 2011-06-21 07:04:28 PDT
We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.
Only the most recently installed version should be marked as current.
Created attachment 3531 [details]
Patch against OJS 2.3.5
Created attachment 3532 [details]
Patch against OJS 2.3.5 (apply against lib/pkp + see db fix below)
Patch marks old version as no longer current for manual install.
Patch restores marking of old version as no longer current in VersionDAO.
Need to manually update versions table to fix this bug after an upgrade to OJS 2.3.5:
UPDATE versions SET current = 0 WHERE product = 'ojs2';
UPDATE versions SET current = 1 WHERE product = 'ojs2' AND major = 2 AND minor = 3 AND revision = 5;
Committed to ojs_stable-2_3 and master:
The fix here reverts patch 3490 in Bug 6579 (Can't move custom blocks).
Tested custom blocks on a clean OJS install and customBlockManager version is correctly set to 1 upon install. Custom blocks can also be moved up/down and left/right.