After I did a git pull to update, this loading indicator showed up on all pages of the Dashboard, and never goes away: http://puu.sh/rvBwM/e3bcf34cbd.png
Also, whenever I open a page such as Submissions or Users, I get this error: {“status”:true,“content”:"\n\n\t\t\tHelp\n\t</a>\n\n\n\n
This is urgent, as my journal starts accepting submissions for its next issue on Wednesday…
EDIT: Getting this error in Firebug: TypeError: $(…).pkpHandler is not a function
Did you ensure that your application’s repository is using the same branch as the submodule in lib/pkp? Did you change from one branch to another, and if so, which branches?
Regards,
Alec Smecher
Public Knowledge Project Team
It would be really odd for the php error log to be exposed in a Web accessible location like public_html or the OJS root. What server are you running under? For example, RHEL would place the error log in /var/log/httpd/.
What is the output of a git status and git remote -v?
Also, when on a shared server with multiple virtualhosts, the system administrator will usually setup your apache access and error logs to be accessible outside of the default CentOS location. Check with your sysadmin on if this has been or can be setup. Availability of the logs will make your troubleshooting so much easier.
The OJS source files (what you would download via git or a tgz)
The OJS data files (this live in files_dir and public)
The OJS database
It is important to know this structure as you perform your regular backups.
The settings and data are held in the data files and in the database. The source files are what are tracked by git, and these can be changed without data loss, provided you also accompany the change of the source with running the upgrade script to make any needed datafile/database changes with an upgrade.
If you refresh the OJS source files, change the file permissions appropriately, and follow the UPGRADE documentation, you won’t lose settings and data. In your particular case, unless the initial run of the 3.0 upgrade failed, or unless the you are re-upgrading from 2.4.x, you don’t need to re-run the upgrade script.
You will probably then need to rerun composer from the lib/pkp directory. I haven’t actually tested this, and I’ve had personal frustrations with the git clean command in the past.