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 check will invalidate a session if the user's IP address changes.; Enabling this option provides some amount of additional security, but may; cause problems for users behind a proxy farm (e.g., AOL).session_check_ip = On

There are several things happening there and I think a few of them are red herrings. The looping problem is probably unrelated to HTMLPurifier or your allowed HTML tags. During the database upgrade process, do you receive any errors?

I'll make the changes in the data base and continue to upgrade to 2.4.2.

Thanks for your help on this.

**Edit for more information**

I do have a question though. Looking at the database for my 2.2.0 install, the status code is set at "1" for these articles and they load fine. Is there some change in the way that 2.2.0 and 2.3.7 handle this status?

The status for published articles should always be 3; previous releases, as you've seen, didn't properly set the status depending on what editorial process you were using, and an enforced check to the publishing front-end was only added recently.