I have installed version 3.2.1.2 of OJS on windows hosting through softaculous. When I login to the admin panel, I see at the bottom error: There are no readable files in this directory tree. Are safe mode or open_basedir active? and when I try to create a new journal, the save button keeps on processing but never gives any error or create the new journal. Why I am getting this error? Any help would be highly appreciated.
Another user has posted a similar error here and offered a solution, for this specific error:
Please do search the forum prior to posting questions as they may have been answered in previous posts, and we would like to avoid duplication where possible.
Dear @rcgillis, yes, I already checked the previous posts. My issue is different and I have already applied the solutions presented before.
This is the home page when I login:
and when I try to create a new journal, even without selecting the option “Enable this journal to appear publicly on the site”, the SAVE button never proceeds further and does not even give any error nor:
Thank you for clarifying and providing screenshots. Do you have access to any error logs on your server through your hosting that you might be able to see what is causing this issue? If not, you may want contact your webhost to see if they can provide anything to determine where the error is occurring.
Thanks for your reply @rcgillis. In the PHP error log, there are no errors shown for the website.
Is it possible to see custom error log produced by OJS application that we can check at our end?
The save button only works in the saving admin user profile setting. Everywhere else in the site administration the save button keeps on rolling and does not produce any output.
Are you able to post the output of your log here to see if we might be able to spot any issues? Any errors would be reported in your server’s web logs and are not specific to OJS per see, but activity on your server, which might give some indication of when/why this error is occurring.
We’ll be releasing OJS 3.2.1-3 to fix this very shortly – I’d recommend either applying the patches on that issue, or waiting for 3.2.1-3 to be released.
Thanks,
Alec Smecher
Public Knowledge Project Team