Since we upgraded to OJS 3.1.2, one of our journal wich uses the most OJS is having a lot of problem that prevents him from using the software normally: problems of displays, validation, etc.
Until we understand where all these problems come from we would like to come back to the previous release and downgrade from OJS 3.1.2 to OJS 3.1.1.
Do you think we can do that without trouble ? I think for example to the DB schema which as changed.
Thanks in advance dor your answer.
Best regards.
Helene
There were more than just db schema changes, there were also SQL commands that executed fixes on the actual database content, e.g. the contents of dbscripts/xml/upgrade/3.1.2_update.xml
My advice is, if you really want to go back to 3.1.1, is to restore from a backup.
@hcl, can you describe the problems youâre having with 3.1.2 in more detail? Itâs been a stable release from our perspective. Itâs possible that it can be resolved without too much trouble, and that might be better than reverting to 3.1.1.
Regards,
Alec Smecher
Public Knowledge Project Team
Here are some problems that one of our journal encounter:
Name and given name of users are not displayed anymore in the backend: maybe related to this issue which is still open
Keywords field of a published submission in metadata doesnât display (maybe a problem of browser because I donât reproduce the problem)
When editorial manager wanted to assign an article to an issue with âSchedule for publicationâ and clicked to the save button, it was loading for ever and never saved
When I retried to do it, it took time but it worked with this messages in error log file:
PHP Warning: Cannot use a scalar value as an array in /var/www/journals/lib/pkp/classes/core/DataObject.inc.php on line 133, referer: https://[journal]/submissions
When editorial manager wanted to access to editorial history of a submission, it was loading for ever and never display.ed There is this error in log file:
PHP Fatal error: Uncaught Error: Call to a member function getFullName() on null in /var/www/journals/lib/pkp/classes/user/UserDAO.inc.php:465\nStack trace:\n#0 /var/www/journals/lib/pkp/classes/log/EmailLogEntry.inc.php(129): UserDAO->getUserFullName(â0â, true)\n#1 /var/www/journals/lib/pkp/controllers/grid/eventLog/EventLogGridCellProvider.inc.php(96): EmailLogEntry->getSenderFullName()\n#2 /var/www/journals/lib/pkp/classes/controllers/grid/GridCellProvider.inc.php(49): EventLogGridCellProvider->getTemplateVarsFromRowColumn(Object(EventLogGridRow), Object(GridColumn))\n#3 /var/www/journals/lib/pkp/classes/controllers/grid/GridHandler.inc.php(1098): GridCellProvider->render(Object(Request), Object(EventLogGridRow), Object(GridColumn))\n#4 /var/www/journals/lib/pkp/classes/controllers/grid/GridHandler.inc.php(1005): GridHandler->_renderCellInternally(Object(Request), Object(EventLogGridRow), Object(GridColumn))\n#5 /var/www/journals/lib/pkp/classes/controllers/grid/GridHandler.inc.php(982): GridHandler->renderRowInternally(Object(Re in /var/www/journals/lib/pkp/classes/user/UserDAO.inc.php on line 465, referer: https://[journal]/workflow/index/xxxx/x
Itâs maybe related to problem of Name and given name of users are not displayed anymore ?
When editorial manager wanted to assign a copyeditor to a submission, the user who has the role of copyeditor doesnât display in the list even after search
I have to leave for a few days and Iâm afraid that the users of the journal will be blocked.
They did not have all these problems with OJS version 3.1.1
But I think there are several problems that have accumulated: We upgraded to OJS 3.1.2. To do that, I had to upgrade to PHP7, and to fix our plugins and specific themes that were no longer compatible with OJS 3.1.2
And there are some issues with OJS version 3.1.2
Thanks in advance for your answer.
Kind regards.
Helene
If there is no chance to restore from the backup, perhaps it might be wiser to wait for the 3.1.2-1, since most of those issues have already been filed.
At least, we (after a thorough testing) are waiting for the next release.
I saw that some of issues are indeed solved in release OJS 3.1.2-1. If I download current stable release 3.1.2 , does it already included the 23 closed issues of next release OJS 3.1.2-1?
And what about my issue 1): Name and given name of users are not displayed anymore in the backend: maybe related to this issue which is still open ?
Did you find the problem and will it be included in the next release OJS 3.1.2-1 ?
Thank you for your support, your responsiveness. I feel a little more reassured now.
Kind regards.
Helene
We have upgraded our journals to OJS 3.1.2, article Schedule for publication is unable to save, it was loading for ever and never saved.
Here is error log with few other issues.
[24-Apr-2019 23:54:15 UTC] PHP Warning: Declaration of AddThisPlugin::register($category, $path) should be compatible with LazyLoadPlugin::register($category, $path, $mainContextId = NULL) in /home/psmpu6586/journals.psmpublishers.org/plugins/generic/addThis/AddThisPlugin.inc.php on line 0
[24-Apr-2019 23:54:15 UTC] PHP Warning: Declaration of CustomBlockPlugin::getBlockContext() should be compatible with BlockPlugin::getBlockContext($contextId = NULL) in /home/psmpu6586/journals.psmpublishers.org/plugins/generic/customBlockManager/CustomBlockPlugin.inc.php on line 0
[24-Apr-2019 23:54:15 UTC] PHP Warning: Declaration of DRIVERDAO::setOAI(&$oai) should be compatible with PKPOAIDAO::setOAI($oai) in /home/psmpu6586/journals.psmpublishers.org/plugins/generic/driver/DRIVERDAO.inc.php on line 19
[24-Apr-2019 23:54:15 UTC] PHP Warning: Declaration of OpenAIREDAO::setOAI(&$oai) should be compatible with PKPOAIDAO::setOAI($oai) in /home/psmpu6586/journals.psmpublishers.org/plugins/generic/openAIRE/OpenAIREDAO.inc.php on line 0
[24-Apr-2019 23:54:16 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADODB_Cache_File has a deprecated constructor in /home/psmpu6586/journals.psmpublishers.org/lib/pkp/lib/adodb/adodb.inc.php on line 263
[24-Apr-2019 23:54:16 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADOConnection has a deprecated constructor in /home/psmpu6586/journals.psmpublishers.org/lib/pkp/lib/adodb/adodb.inc.php on line 359
[24-Apr-2019 23:54:16 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADORecordSet has a deprecated constructor in /home/psmpu6586/journals.psmpublishers.org/lib/pkp/lib/adodb/adodb.inc.php on line 2921
[24-Apr-2019 23:54:16 UTC] PHP Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; ADORecordSet_array has a deprecated constructor in /home/psmpu6586/journals.psmpublishers.org/lib/pkp/lib/adodb/adodb.inc.php on line 3939
[24-Apr-2019 23:54:17 UTC] PHP Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/psmpu6586/journals.psmpublishers.org/lib/pkp/lib/adodb/adodb.inc.php on line 1003