- After moving the OJS to another server we experience problem with Settings - Journal - Masthead and Contact.
- Same problem we get on Submissions - active
This pages show blank page. No error message.
We are using OJS 3.0.0.0
Can any one help?
We are using OJS 3.0.0.0
Can any one help?
Hi @gine001,
See this FAQ entry. I would also suggest upgrading to a more current release.
Regards,
Alec Smecher
Public Knowledge Project Team
Ok will check that.
I would like to make it work before upgrading, upgrading can cause another issues instead.
I tried with the solution you given, but no change.
Thanks for your support
Upgrading to 3.0.2
Getting blank page on:
http://www.mydomain.com/journal/index.php/index/install/installUpgrade
The installation got stuck! Anything recommended?
Hi @gine001,
Did you look into the FAQ entry I posted above? What results did you get?
Regards,
Alec Smecher
Public Knowledge Project Team
Yes, We tried all that but can’t get any error or changes.
We are now trying on another server.
The first one is Centos 6.4
Hi @gine001,
It’s extremely likely that there’s an error message in your PHP error log, so make sure you’ve checked it.
Regards,
Alec Smecher
Public Knowledge Project Team
Now most of the OJS is working, that is after reinstalling the Journal to 3.0.2.
But we still have problems with Plugins. That is not showing. Just spinning…
Any one with the solution for that?
Hi @gine001,
Again, please check your PHP error log. It will probably contain details.
Regards,
Alec Smecher
Public Knowledge Project Team
It will be helpful if we new what we are looking for.
Do you have some kind of “example error message” for some plug-ins?
Hi @gine001,
You’ll want to watch the log file to see what new messages appear in it when your server hits the problematic page. The relevant message will probably say something like “Fatal Error” in it.
Regards,
Alec Smecher
Public Knowledge Project Team
Sorry.
i have run several “grep” options on all error_log files on our server.
No errors of such, that refers to the OJS(journal installation).
Hi @gine001,
Rather than grepping for the right file, I would suggest looking at your phpinfo
output to ensure you know where to look.
Regards,
Alec Smecher
Public Knowledge Project Team
This is a very strange and not constructive answer.
There are no errors in the error_log files. Some minor warnings only.
Any other solutions?
Is there a debug mode?
Hi @gine001,
Your server will have several error logs and it’s important to ensure you’re looking at the right one in order to debug this systematically. You mentioned that you were grepping through multiple log files, which suggested that you might not be sure where to look. Did you check your phpinfo
output? Look in it for e.g. your error_log
configuration directive.
Regards,
Alec Smecher
Public Knowledge Project Team
We are sure where the error log for the ojs resides. The problem was that ojs didn´t give any “fatal error” at all, just [warn].
After reinstalling ojs, we could see how it works and could generate “PHP Fatal error:”.
So Submission problem is partly solved.
We still have problems with the publishing of submissions. When clicking on “More Information”, getting alert window: “Failed Ajax request or invalid JSON returned”
Here is the error_log message:
[Tue Jun 27 17:01:17 2017] [warn] [client 79.102.98.166] mod_fcgid: stderr: PHP Fatal error: Call to undefined method InformationCenterHandler::InformationCenterHandler() in /oursite.com/journal/lib/pkp/controllers/informationCenter/PKPSubmissionInformationCenterHandler.inc.php on line 25, referer: http://journal.oursite.com/index.php/oursite/submissions
Hi @gine001,
Is it possible that you’re mixing code together from different versions of OJS? Are you still using OJS 3.0.0.0?
Regards,
Alec Smecher
Public Knowledge Project Team
we upgraded from 3.0.0 to 3.0.2, unfortunately it didn’t go 100%…
what file is replacing the one causing the error?
After submitting users getting email,
“email received but no way to get the link for downloading the paper.”
Available for reviewing.
What is the problem there?