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.
Try manually updating the adminUsername and encryptedPassword settings in the site_settings table. To create a hashed password, use the md5 or sha1 function in MySQL (depending on what hashing method you chose on the setup form) as follows:
We tried that, but couldn't do it. What happened was that the system was logging in a different server, I don't know how this was done. We managed to recover the password anyway..
However, we tried a fresh install, it went through ok, but the login did not work. We may need to test this further, but I'd like to know if there are login problems you are aware of after installation, what server config could prevent this from working...
Strange -- do you mean that the submit form is being sent to another server? There are no long problems that I'm aware of, but of course the Harvester isn't as widely deployed as OJS or OCS. Send me some detail on the problem and I'll see what I can turn up.
Regards, Alec Smecher Public Knowledge Project Team
That's the thing, I don't have the details since I'm not in charge of the service here. All I know is that we tried to a new installation using the same database, but could not login at all. We figured out after a while that the login form was being sent to another server. Apparently, the harvesting is being done through a remote server, then sent to this other one we couldn't login.
I'll have to run further tests, but I have no time currently. I'll need to set up a team to work on this since the person responsible is leaving soon...
Please note that after updating the database, you must flush the old value out of the cache. I lost an hour or so staring at the code, trying various tools to generate the hash (getting the same value each time), inserting error_log() calls to peek at values being developed, etc. before I realized this.