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've already checked the FAQs for installation problems and tried some of the suggestions there, but nothing seems to be fixing the issue that I'm having. I tried to install version 2.3.8 and then moved to 2.4.2 and am having the same problem with each: the installation form loads successfully, but after clicking the button to install, a blank page appears and the database was not created. I verified with phpinfo(); that the module for PHP/PostgreSQL is installed and see the following:

PostgreSQL Support enabledPostgreSQL(libpq) Version 8.4.11Multibyte character support enabledSSL support enabledActive Persistent Links 0Active Links 0

per the comments in php.ini, modules are loaded dynamically from the php.d directory

I tested to see if php was interacting correctly with postgresql by creating a very simple php script with a SQL select statement that I ran from the same directory as where I've installed OJS and the script worked correctly.

Hence my confusion; I'm not sure why PHP believes output is being generated at that line. (The output it mentions could be a warning or error message; if so, make sure you quote it.) These "cannot modify header information" warnings are themselves harmless, but they can prevent redirects and the like and may indicate problems elsewhere.

Make sure you restart your Apache process after you adjust php.ini settings; if you're using mod_php or FastCGI or the like, changes won't take effect until you do.

Ok... I know why that error message is showing up there... I'd edited functions.inc.php to add the line to output classes as they are called per some suggestions in the faqs - that change was right around line 23. I later deleted the line as I didn't see anything useful from that output.

I've made no other changes to the source code.

As to restarting Apache after modifying php.ini - yep... that's what I've been doing.

Your installation is behaving exactly like it would if the PostgreSQL module was missing -- blank screen, no error message, with the URL you've noted above. A good debugging next step would be to verify that the pg_... functions work when called directly, which is what you've already done. Unfortunately debugging a blank screen with no error message doesn't give one much to work with and it's one of the pernicious things about PHP. The next step I'd recommend will be to find out how far the script gets before it dies, and unfortunately there's no more elegant way to do this than to go to various points in the system and add "die(...);" messages, trying again as you go. I'd suggest starting with lib/pkp/classes/install/Installer.inc.php in the "execute" function -- that's where the actual installation process happens.

One note -- before you do this, it's worth spending a little time figuring out your PHP error message configuration. It would be annoying to spend time trying to debug a blank screen only to discover that error messages were helpfully logged somewhere you weren't looking. Your phpinfo() output is the definitive resource here -- but make sure that you're testing with the same environment you're working in; some servers will have one php.ini for command-line access and another for web-based access.

This is actually my first experience with open source - too bad it's gone this way (which I know is not the fault of the software), but I'm glad for the experience and to see how community support works.

We went ahead and wiped the server and rebuilt it, this time enabling MySQL instead of PostgreSQL and I have now been successful with the install. I wonder if there's some issue with the way that PostgreSQL is set up on CentOS that causes this failure. If anyone should happen to run into this/have a solution, I'd love to know, because I do have a VERY slight preference for PostgreSQL.