OJS 2.3.5 Released

[michael]

The PKP Development Team is pleased to announce the release of OJS 2.3.5.

OJS 2.3.5 builds upon the successful 2.3.4 release by incorporating the recommended patches (http://pkp.sfu.ca/wiki/index.php/OJS_2.3.4_Recommended_Patches) for that release.

This release includes an important fix to how OJS exposes publication date information to Google Scholar. (Many thanks to Anurag Acharya and his team at Google Scholar for notifying us of the problem, and for their continued help towards a fix). Previously, any article published via the Expedited Submission or Quick Submit publication processes appeared to the search engine to be published on the date it was submitted to OJS, rather than on any previous given publication date (as would be the case with back issues).

Upgrading will ensure that affected article publication dates will appear more accurately in Google Scholar. The fix may modify your article publication date data. If you have published articles via either of these two methods, please backup your database and verify the integrity of your publication date data following the upgrade.

This release also includes an enhancement that allows Editors to be able to manually set publication dates.

For more information, please see:
- http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=6480
- http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=6497

For release notes, please see http://pkp.sfu.ca/ojs/RELEASE-2.3.5. OJS 2.3.5 can be downloaded at http://pkp.sfu.ca/ojs_download.

Many thanks to all of the contributors who made this release possible.

[mvluijt]

Hi guys,

Just did an upgrade from 2.3.4 to 2.3.5 on a local machine (essentially an empty installation) and ran into an issue with the 'about this publishing system' page failing, complaining about two active current versions. Sure enough, both 2.3.4 and 2.3.5 of the 'core' product were present and current in the 'versions' table. Deleted the 2.3.4 entry and all was well.

Best, Martin

[michael]

Hi Martin,

Thanks for the bug report. I can confirm that we've reproduced it and we'll have a fix shortly.

Rather than deleting the older version records, you can simply set current = 0 for these:

Code: Select all

 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;

Cheers,
Michael

[michael]

Full details for this bug can be found here.

Please feel free to post any additional issues with this problem directly into the bug report.

Cheers,
Michael