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.

There's a bug with paypal payments when the payment amount is containing a decimal mark and you're using OJS in a country / locale setting, where the decimal mark is represented by a comma instead of a period. The payment form page, as created by the template "paymentForm.tpl" will contain a locale-specific form of the amount to be paid, e.g. "amount=2,90" instead of "amount=2.90". Paypal reacts to the POST-message containing this number with an error message, saying that the number is not formatted correctly and thus the payment could not be processed.I'm not sure where exactly the locale aware formatting of the payment amount takes place. However, a possible workaround is this:

In line 120 of "PayPalPlugin.inc.php" format the amount with the non-locale aware version of sprintf, i.e. %.2F:

Just a heads-up -- your fix turns out to work well for the general case (see the link cited in the Bugzilla entry). Thanks for contributing; this has been committed to OJS, OCS, and OMP and will be included in the next release of each.