Hi,
we are trying to upload XML and HTML in galleys. We tried through Quicksubmit plugin as well as from submissions. When we Upload these types of file , the system just hangs up and doesn’t do anything.
OJS site was having issue with PDF hanging also but most of the PDF’s were getting attached. However for XML and HTML, nothing is going through. Is there something we need to check in these files to be sure we don’t get errors.
Browser console throws this error : Uncaught SyntaxError: Unexpected token ‘<’, “<hea”… is not valid JSON
** at jQuery.parse [as parseJSON] ()**
I cleared cache also but it didn’t work. Nothing comes up in the Logs.
OJS version 3.3.0.13
Hi @deepakc,
It looks like your OJS installation is responding with HTML to what should be a JSON request. The likeliest cause for this is that your system has been hacked to serve up spam content; we’re aware of automated attacks against outdated 3.3.0-x installs that might result in this. I’d recommend checking over your installation, updating to the latest 3.3.0-x or 3.4.0-x release, and changing any admin or journal manager passwords.
Regards,
Alec Smecher
Public Knowledge Project Team
We are planning to upgrade from OJS 3.3.0.13 to 3.5.* and are currently awaiting for 3.5 stable release. In the meantime, isn’t there something we can do at the OJS level to address this issue?
This is a severe problem, causing significant difficulty for editors. It’s worth noting that OJS isn’t experiencing this issue across all uploads; we are still able to upload some files - XML, PDFs, and HTML successfully.
Hi @deepakc,
The upgrade from one 3.3.0-x release to another should be quick and reliable, and shouldn’t change any features for editors – it should just work better. We’re due to release 3.5.0 on June 16th, but note that it won’t initially have the LTS stamp on it; we’ll likely have another build or two before we consider it ready for LTS usage. I’d recommend a quick upgrade to the latest 3.3.0-x, followed by an upgrade to 3.5.0 at your leisure.
If you want to debug what’s happening, I’d suggest using the Network tab in your browser’s developer tools to inspect the server response that’s accompanying the Javascript error message. It’ll give you a hint bout what the server is sending instead of the expected JSON message.
Regards,
Alec Smecher
Public Knowledge Project Team
