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.

We have a journal still on version 1.1 for a number of reasons. We did an OS upgrade on the server in which resides last month and the editor discovered his login failed. The tblusers is intact, and I can do a query on users through SQL, but I think there is a problem with the encoding process in login.php. I see in the code there is this $passwd_salt, but I had no idea what it meant. Then in my password agent application I discovered that I have a password salt key listed, but I have no idea what to do with it to ensure the login process will work. I can't find documentation to tell me what I might need to do in order to get the login to read this password salt properly.

If you don't get coherent passwords back, it's probably because the MySQL ENCODE and DECODE functions are behaving differently or the DBMS upgrade changed the character set configuration. You may need to restore your database on an older version of MySQL and migrate the passwords manually. If you're able to get the passwords to decode coherently on another machine, I can provide instructions on the migration process.

The loginUser function in login.php, which is responsible for logging users in, is not written in OJS 1.x to deal with MySQL errors. I'd suggest turning on MySQL query logging temporarily to find out what queries it's running (or if it's running them at all); then proceed from there to debug further.