As the developers of Open Journal Systems, Open Conference Systems, Open Harvester Systems, and Open Monograph Press, the PKP team are experts in helping journal managers and conference organizers make the most of their online publishing projects. PKP Publishing Services offers support for:

As a customer of PKP Publishing Services, you will not only receive direct, personalized support from the PKP Development Team, but will be contributing to the ongoing development of the PKP applications. All funds raised by PKP Publishing Services go directly toward enhancing our free, open source software. For more information, please contact us.

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

I'm using an "Email-Attachment Review Process". I receive a manuscript, i select and assign a reviewer from the list of registered reviewers and i click on the mail logo in order to send the request. the OJS gives me a default email where i ask the reviewer to collaborate but when i click on SEND but i receive two different errors then:

1) * Error Code 64: Host not available
* Background: The connection to the Web server was lost.

This problem comes out when the attachments pass 300kb. Is there a specific setting that i can edit? i only found the maximum file upload size which is set to 2Mb. i found a "HTTP_KEEP_ALIVE=300" under Apache Environment and a "Keep_alive=300" under HTTP Headers Information... could it be one of these?

Apache 2.x has a LimitRequestBody directive that, if set to a low number, can lead to this behaviour. In particular, the default PHP packages for recent versions of Red Hat Linux set LimitRequestBody to 524288 bytes in /etc/httpd/conf.d/php.conf.

Low values for the PHP ini settings like post_max_size (default "8M"), upload_max_filesize (default "8M"), and memory_limit (default "8M") can also cause this problem.

Some firewall products cause this kind of problem by watching for particular kinds of content in request strings; one product, for example, blocked all requests containing the words "DELETE" and "FROM" in that order in a misguided attempt to block SQL injection attacks. Of course, that content may well appear in a valid request, particularly as the request gets longer. I'd suggest that you try toying with your firewall, if you're able, to see if it's being accidentally triggered by the request.