cgi-system

[jasonnolan]

I'm trying to move a 1.1.9 version of OJS over to dreamhost. And I keep running into 3 problems.

1) it keeps looking for cgi-system in the path which doesn't exist nor has it ever in the previous version of the install. How do I make it stop looking there? the software's useless under these circumstances.

2) http://harrow.domain.org/journal/admin/ ... editor.php shows that all the articles are missing. For myself and the other editors. The articles are in teh system, but just not showing up in this view.

3) when I exported the sql db it came as latin1_swedish_something. What's with that? When I tried importing as UTF-8 the passwords didn't work (yes, I copied the salt.)

Any help greatly appreciated. I will upgrade to 2.x as soon as this is working.

J

[asmecher]

Hi Jason,

1. See http://drupal.org/node/60139 for a discussion of the cgi-system issue -- looks to me like a server configuration issue.

2. This URL isn't currently working -- could you describe the problem a little further? Are you unable to access the submission files, or are the entries in the database itself not showing up?

3. OJS 1.x uses Latin1 by default; you might have trouble trying to use UTF-8. You may be able to transcode using a tool like iconv, but I suspect that the encode and decode functions won't like this. My suggestion is this: do the database dump and load, and use a separate set of queries and updates to correct the passwords. Rather than trying to dump the encoded values into the new database, decode the actual passwords and re-encode them on the new machine. You might need to write a little script to help with this -- I can provide more details if you like.

Regards,
Alec Smecher
Open Journal Systems Team

[jasonnolan]

thanks alex. the drupal issue does give me some clear leads. I'll try them then see where that leads me and let you know if we have any more questions. Much appreciated.

[jasonnolan]

Hi Jason,

1. See http://drupal.org/node/60139 for a discussion of the cgi-system issue -- looks to me like a server configuration issue.

2. This URL isn't currently working -- could you describe the problem a little further? Are you unable to access the submission files, or are the entries in the database itself not showing up?

3. OJS 1.x uses Latin1 by default; you might have trouble trying to use UTF-8.

1. I tried what they suggested in turning off Extra Web Security
and FastCGI Support, but it didn't change anything. My hosting person says that

#3 doesn't seem to be a problem. I imported it as latin1

2. When I go to the site to view static or produced pages, everything's fine, but when I go to http://harrow.lemmingworks.org/journal/login.php and log in I get to http://harrow.lemmingworks.org/cgi-syst ... editor.php which is 404. If I manually edit it to http://harrow.lemmingworks.org/journal/ ... editor.php everything's fine for a while until I trip over something, and we get /cgi-system/

My guy says that that's really just an error getting thrown up. He's trying to help me find where $vars['refer'] is set so that we can either change it, or manually over-ride it.

We finally edited include/common.php and commented out the following, adding a hard coded line for the base url. Is that OK? Is there a FIX that we can use that will survive when we upgrade to version 2?

// Kludge to define base URL dynamically
// Probably will not work if using PHP CGI
// $commonDirname = dirname(dirname(__FILE__));
// $scriptDirname = dirname($_SERVER['SCRIPT_FILENAME']);
// $scriptDirname = substr($scriptDirname, strlen($commonDirname));
// $scriptPath = preg_replace('/' . preg_quote($scriptDirname, '/') . '$/', '', dirname($_SERVER['SCRIPT_NAME']));
// $baseurl = (isset($_SERVER['HTTPS']) ? 'https' : 'http') . '://' . $_SERVER['HTTP_HOST'] . $scriptPath . '/';
$baseurl="http://mydomain.org/journal/";
}

Thanks!

[asmecher]

Hi Jason,

Glad to hear you've got it working again; while hard-coding the URL isn't the subtlest of fixes, it's certainly effective and I'd suggest going ahead with it.

When you upgrade to OJS 2.x, you might find that whatever is causing the problem with OJS 1.x "goes away" -- I've never encountered this sort of problem with OJS 2.x, and the codebases are entirely different. If you do have trouble... post here.

Regards,
Alec Smecher
Open Journal Systems Team

[jasonnolan]

I'm still getting two strange errors. Any thoughts?

First the "active editorial assignments" is not getting updated, and has lost anything that was in the system before it was moved, though it is in the submission queue.

And:

Warning: mysql_query(): supplied argument is not a valid MySQL-Link resource in
/home/blaa/harrow.lemmingworks.org/journal/include/db/db.mysql
.inc.php on line 58

Warning: session_start(): Cannot send session cache limiter - headers
already sent (output started at
/home/blaa/harrow.lemmingworks.org/journal/include/db/db.mysql
.inc.php:58) in
/home/blaa/harrow.lemmingworks.org/journal/include/session.inc
.php on line 64

much thanks. We're really close

[jasonnolan]

I'm having exactly the same problem trying to install version 2.1.1 that I had with version 1.1.9, except our previous solution was to hard code the basedirectory URL in include/common.php, which doesn't exist.

any suggestions as to how we can hard code the URL so that OJS doesn't keep looking for cgi-system:

http://theharrow.com/cgi-system/index.php/index/search

the install is at http://theharrow.com/journal2007/ so I would expect things to start there.

Thanks for any suggestions.

Hi Jason,

Glad to hear you've got it working again; while hard-coding the URL isn't the subtlest of fixes, it's certainly effective and I'd suggest going ahead with it.

When you upgrade to OJS 2.x, you might find that whatever is causing the problem with OJS 1.x "goes away" -- I've never encountered this sort of problem with OJS 2.x, and the codebases are entirely different. If you do have trouble... post here.

Regards,
Alec Smecher
Open Journal Systems Team

[jasonnolan]

if anyone runs into this problem again, just let it be known that by adding a .htaccess file in the root directory with the line "AddHandler application/x-httpd-php .php" (without quotes) will 'solve' the problems. This is unsupported and not recommended by dreamhost.com, but it does work.