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 tried again to manually fix the tables. This time I copied the data from old to new. Most of the pages can be displayed but not home and current. There is a list of issues on archives page but when I clicked on the link to any issue, the page cannot be displayed (error). Again, if I log in as editor role, all the submission stats are 0. If I click the in review or in edit links, I get this error:

I am working on copies of the OJS files and database. I want to make sure there is no problem with the upgrade before I make it online. In another word, I am still having my production OJS live which will not be affected by my upgrade testing.

I make an identical copy of my current database via myphpadmin, and do the upgrade. After each failed database upgrade, I delete this database, and make another copy and try it again.

The collation error message is coming from MySQL; it suggests that you're somehow mixing Latin1 and UTF8 content in your database. I suspect your copy is in Latin1 and your original database is UTF8, or similar.

My original (current) database uses utf8_general_ci and gbk_general_ci. At the bottom of the table list, it shows "MyISAM" as type, and "latin1_swedish_ci " as collation.

The upgraded database uses the same mixture of utf8_general_ci and gbk_general_ci; however some tables including those problematic ones may have the same or different collation compared with the original ones. I tried different the database (not table) collations but it didn't help.

Are your config.inc.php connection_charset and database_charset options the same in the upgrade installation? OJS doesn't do anything funky with database character sets, so if those settings are the same in the two installations, then the conflict is most likely introduced when you're making a copy.

I compared the two databases. OJS 2.3.3 has 99 tables and 2.4.2 has 123. Some tables in 2.4.2 may not be populated. For example, a number of issues related tables are empty. I wonder if this is causing the problem.

Apparently the database problems occur to article and submission related tables because others, e.g., user login, announcements etc, are working just fine.

One of the main reasons I want to upgrade is my hope to get the review invitation email interface working probably with the newer version without going into other trouble. Right now when I send a request to reviewer, I can't add recipients to the CC and BCC fields. In fact, all email addresses fields (including the "To" field") are grayed out and inaccessible. Looks like there is no quick fix. I wonder if you could help me with this too.

What are your thoughts about my earlier comments (I compared the two databases. OJS 2.3.3 has 99 tables and 2.4.2 has 123. Some tables in 2.4.2 may not be populated. For example, a number of issues related tables are empty. I wonder if this is causing the problem. Apparently the database problems occur to article and submission related tables because others, e.g., user login, announcements etc, are working just fine.)?

I have a couple of stupid questions: Does the upgrade script populate those new tables with data grabbed from existing tables? What if these data are not available?

The upgrade script is in charge of creating additional tables and populating them as necessary. There will be a number of additional tables in OJS 2.4.2 and many will be created without content; that's fine.

The code preventing editors from changing the addressing of reviewer emails is in classes/submission/sectionEditor/SectionEditorAction.inc.php: