Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.
Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher
The Public Knowledge Project Support Forum is moving to http://forum.pkp.sfu.ca
This forum will be maintained permanently as an archived historical resource, but all new questions should be added to the new forum. Questions will no longer be monitored on this old forum after March 30, 2015.
OS: Redhat ES4
We recently moved our OJS (2.0.2) installation to a new server; copied the database (mysql), the ojs directory and the ojs-files to the new server in the same locations as before.
Now - for the public view, one can see the table of contents, but the html produces an empty page; Also, for the administrations side: all of the management pages for Editor, Section Editor, etc generate empty pages.
The old box was Apache 1, the new is Apache 2; I believe we also moved from a MySQL v3 to v4.
How does one migrate to a new server successfully?
- Posts: 15
- Joined: Fri Sep 30, 2005 11:35 am
Two things to check:
- Make sure you're able to see error messages if there are any; these will help determine the problem. Set display_errors to E_ALL in php.ini, restart the web server, and try viewing the site again.
- Check to make sure file permissions are set properly. The web server user (typically www-data or nobody) needs to be able to read and write files in the following directories:
- OJS files directory (as configured in php.ini)
- public directory
- cache directory
- cache/t_compile directory
- cache/t_cache directory
- cache/_db directory
- cache/t_config directory
Open Journal Systems Team
- Posts: 10015
- Joined: Wed Aug 10, 2005 12:56 pm
Return to OJS Technical Support
Who is online
Users browsing this forum: Bing [Bot] and 3 guests