Reviewer submission error

When reviewers attempt to submit their review they get an error such as the one below or the time thing just goes round and round and nothing gets saved.

One example is this:

Fatal error: Uncaught Error: Non-static method AccessKeyManager::generateKeyHash() cannot be called statically in /home/murmur/public_html/ojs/pages/reviewer/ Stack trace: #0 /home/murmur/public_html/ojs/pages/reviewer/ ReviewerHandler-_validateAccessKey() #1 /home/murmur/public_html/ojs/lib/pkp/classes/core/ ReviewerHandler-authorize() #2 /home/murmur/public_html/ojs/lib/pkp/classes/core/ PKPRouter-_authorizeInitializeAndCallRequest() #3 /home/murmur/public_html/ojs/lib/pkp/classes/core/ PKPPageRouter-route() #4 /home/murmur/public_html/ojs/lib/pkp/classes/core/ Dispatcher->dispatch() #5 /home/murmur/public_html/ojs/index.php(68): PKPApplication-execute() #6 {main} thrown in /home/murmur/public_html/ojs/pages/reviewer/ on line 78

Steps I took leading up to the issue
None so far.

What application are you using?

Hi @gail,

This has already been fixed in a later release of OJS 3.3.0-x; I’d suggest upgrading.

Alec Smecher
Public Knowledge Project Team

Okay… I am so nervous of upgrading as the website rarely functions afterwards then I have to reinstall old version…
Please can you advise on best route to upgrade. I try through Softaculous installer normally.
Should i go for the 3.3 LTS version or 3.4?
Installation guidance looks clear but how will it know there is an existing journal and not a new journal?

honestly it’s always a nightmare and am now restoring from backup

Errors occurred during installation:

  • A database error has occurred: There are one or more log files that were unable to finish processing. This happens when the scheduled task to process usage stats logs encounters a failure of some kind. These logs must be repaired and reprocessed or removed before the upgrade can continue. The logs can be found in the folders reject, processing and stage in /home/murmur/ojsfiles/usageStats.

Hi @gail,

You can update within the same line of releases (e.g. from 3.3.0-10 to 3.3.0-17) without even having to run an upgrade script – you just need to update the code. If upgrading is a challenge, I’d suggest sticking with 3.3.0-x and waiting for the next Long-Term Support (LTS) release, which will be 3.5, before making a major jump.

Alec Smecher
Public Knowledge Project Team

This topic was automatically closed after 12 days. New replies are no longer allowed.