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.

The advice to roll back your DB is useful when you're trying to run a DB upgrade on a database that's already failed for some other reason. A failed DB upgrade will leave your DB stranded somewhere between the two versions, so rolling back before you try again is always a good idea.

It sounds to me like the event_log_settings table already exists and contains content, which shouldn't be true of an OJS 2.3.7 database. Can you check your OJS 2.3.7 database dump to see whether that table exists?

I determined that that table was not in my MySQL dump, so I dropped it from the DB, re-ran the upgrade script (and went back and forth with this process a couple times because it was crashing due to PHP resources limits which I then Upped), and viola! All Upgraded!

Now, something disturbing I am noticing: My tables are a mix of MyISAM and InnoDB. Is that OK???

One last question related to this thread: Is there, from the OJS perspective, a preference in table type, MyISAM or InnoDB? I am not averse to changing table types so they are all the same. I'm reading that MyISAM is better for full text indexing, yet is easily corrupted; InnoDB is better for transaction processing. Which one is best for OJS as a whole?

We target both MySQL and PostgreSQL (and may target others), so we're not making use of any particularly advanced database functionality. Both will work just fine. As of MySQL 5.5, InnoDB is the default engine; probably best to stick with that for sheer simplicity's sake.