Thanks for reporting! I’ve filed this for attention here:
There is a patch to fix the issue with OJS 3.2.x, but I don’t think we’ll likely back-port the fix to OJS 3.1.x, which is now quite old. I’d recommend upgrading to something that includes the fix. (We’ll be releasing OJS 3.2.1-2 with this fix included likely within a week or two.)
Regards,
Alec Smecher
Public Knowledge Project Team