hi everyone, we have a self hosted ojs account for our journal, the journal of futures studies. We have encountered a serious problem as all of the submitted papers are not downloadable anymore. Anytime an editor or reviewer tries to click on the link for a submitted paper we get a 500 error. Needless to say the entire journey reviewing has grinded to a halt. We also have several dozen papers under review which are now in limbo. It’s a pretty serious issue
I contacted the hosting company to find out if they could help or diagnose the issue.
They said the problem was with the software in ojs and it was not something that they could help with.
They did look through the software to look for errors and they said they found this particular error below:
[08-Sep-2022 20:47:48 America/Chicago] PHP Fatal error: Uncaught League\Flysystem\Exception: Impossible to create the root directory “/home1/dmhvbdvt/ojsdata”. mkdir(): Permission denied in /home2/dmhvbdvt/ojs.jfsdigital.org/lib/pkp/lib/vendor/league/flysystem/src/Adapter/Local.php:112 Stack trace: #0 /home2/dmhvbdvt/ojs.jfsdigital.org/lib/pkp/lib/vendor/league/flysystem/src/Adapter/Local.php(78): League\Flysystem\Adapter\Local->ensureDirectory(‘/home1/dmhvbdvt…’) #1 /home2/dmhvbdvt/ojs.jfsdigital.org/lib/pkp/classes/services/PKPFileService.inc.php(46): League\Flysystem\Adapter\Local->__construct(‘/home1/dmhvbdvt…’, 2, 2, Array) #2 /home2/dmhvbdvt/ojs.jfsdigital.org/classes/services/OJSServiceProvider.inc.php(51): PKP\Services\PKPFileService->__construct() #3 /home2/dmhvbdvt/ojs.jfsdigital.org/lib/pkp/lib/vendor/pimple/pimple/src/Pimple/Container.php(118): APP\Services\OJSServiceProvider->APP\Services{closure}(Object(Pimple\Container)) #4 /home2/dmhvbdvt/ojs.jfsdigital.org/lib/pkp/classes/core/PKPServices.inc.php(69): Pimple\Container->offsetGet(‘file’) #5 /h in /home2/dmhvbdvt/ojs.jfsdigital.org/lib/pkp/lib/vendor/league/flysystem/src/Adapter/Local.php on line 112
We have already updated to the latest version of ojs… 3.3.0.11
But that has not helped.
Has anyone encountered this problem? Is there a solution?
We’re pretty desperate as this has grinded reviewing to a stop.
Thank you
Jose