@Richard-Higgins and @ojs_univie
First of all thank you both for your testing and contributing to the issue in a much deeper tehcnial level.
Here is a summary of the current status
- The issue you mentioned without the publicationId is very hard to reproduce. As it is not visible in a production environment, we have to guess, that something in the way the sandbox react can cause the issue you mentioned. S In OJS side, we are working on more fine-granular error reporting to enable JMS/JEs or Sys-Admins to find out , if there is a configuration error.
The error in the initial report in this ticket can be more customized to return more concrete values. That we will do from OJS side and may be find out the reason, when this scenario is repeated in future again.