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.

This must be occurring therefore the fields file_name and original_file_name are being limited for 90 characters in the table article_files. This exactly error that occurred with the subject of emails already was corrected.

But the problem cannot be decided with simple truncate therefore would lose the extension of the file... I think...

This can be happening with the supplementary files, I did not test…

We are with the OJS 2.0.1 and Postgresql 7.4. We will make the update soon but I already verified that the error also occurs in version 2.1.

A few field lengths were corrected in OJS 2.1.1 where there was a mismatch between the HTML field maximum length and the database field length; however, you'll still see this error in situations where the database doesn't support UTF8 natively and the content the author enters contains a long title containing special characters. Ensure that your DBMS supports UTF8 natively and try enabling connection_charset and database_charset in config.inc.php; this should correct the problem.

Absolutely right -- I re-read your posting more carefully and I understand the problem now. I've entered a bug entry for this (http://pkp.sfu.ca/bugzilla/show_bug.cgi?id=2411); this should be corrected in our next release, and when I fix the bug, I'll post a patch against OJS 2.1.1.