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.

Dear Colleague, I have one problem. When the author finishes proofreading, he/she has to send a email to inform the proofreader. In OJS .2.4.0, when the author try to send email, the OJS reload the same page (author sending mail page) again and again, so the author cann not finish the proofreading stage. The following is the logPHP Notice: No file uploaded in Unknown on line 0, referer: http://jxxx.xxx.xxx.xxx/index.php/xxxx/ ... icleId=xxxPHP Notice: No file uploaded in Unknown on line 0, referer: http://xxx.xxx.xxx.xxx/index.php/xxxx/a ... plete/send

/pages/author/AuthorHandler.inc.php(123) : Fatal error - Call to a member function getJournal() on a non-objectUnknown(0) : Notice - No file uploaded

Given the 'No file uploaded' notice, the first thing I'd check in your case would be to see whether or not the file that was uploaded was too large. PHP sets limits on the size of uploaded files based on some settings in php.ini. Can you have a look at those settings? The ones of interest would be 'upload_max_filesize' and 'post_max_size'.

Dear Jason,Thank you for your comment, but I don't think it is due to the setting Of php.ini because the values in my php.ini are very large.By the way, the copy editor and layout editor can send mail without problem, The problem occurs only when the author finish proof reading stage and then send a mail to proofreader.Thank you.

I think I know what the problem is. OJS 2.4.0 (and earlier) make use of some PHP functions that have been marked as deprecated in our pkp-lib web application library. From the look of the stack trace, these PHP notices are generating a fatal runtime for you, perhaps due to the Suhosin-patch that you are running on your server instance.

The specific lines of code that are using the deprecated functions have been removed from the current Github version of the master branch and will be phased out in future releases of OJS. Can you make a small change in your code to see if the problem goes away?

Can you change line 113 in classes/submission/proofreader/ProofreaderAction.inc.php to:

Dear Jason,Thank you !The messages disappeared, but the main problem is that the author can not send the "proofreading finish email" out, so she/he can not finish this step, by the way, the status for the active is showed "copyedit request" not "proofreading request" it is strang.

Can you try the problem again, but also include the new stack trace? I have tried to duplicate your problem on my own installation, and I cannot. The debug information you provide will be very helpful.

Dear Jason,The stacktrace is just [Sun Sep 30 06:33:35 2012] [error] [client 42.71.73.178] PHP Notice: No file uploaded in Unknown on line 0, referer: http://***.***.***.***/***/index.php/au ... plete/sendI did not get any more message. I did not upgrade to 2.4.0 successfully at the first time. Perhaps for this reason. my DB was damaged, and it is the reason that I got a lot problems on this release.

Which stems from submitting a form that has a file upload field but leaving it empty. The form you are submitting has a field for attaching a file and it sounds like you are not submitting one. You might also try increasing the error_reporting directive in your php.ini file to something like: