Pair.com cgi adjustments

[rick-k]

Instead of this line at the beginning of your Perl scripts:
#!/usr/local/bin/perl

use:
#!/usr/bin/perl

The first generates errors.

Also, check your domain paths within scripts. Instead of the "/big/dom/xyourname" structure, you'll use something like "/usr/home/yourname/public_html/yourdomain.com"

I didn't have to make any changes to the way SSIs are called within shtml pages. One of the scripts needed one of the above adjustments though.

At least sometimes,
use CGI::Carp qw(warningsToBrowser fatalsToBrowser);
will send warnings and fatal error messages to your browser. If you use that in your Perl script's second line and get an error without anything specific, Perl is probably not getting the Carp command. The problem could be on the very first line--telling where Perl is. If Perl's not at that place, Perl isn't even running. That's why it's not following the Carp command.

Things I never had to worry much about because once you got something to work on FutureQuest you never had to think about it again. I'm sharing in case it helps someone.

[tril]

Originally Posted by rick-k

Also, check your domain paths within scripts. Instead of the "/big/dom/xyourname" structure, you'll use something like "/usr/home/yourname/public_html/yourdomain.com"

The DOCUMENT_ROOT environment variable is useful for this, at least under Apache. (In a Perl CGI you could get it with $ENV{DOCUMENT_ROOT})

[Kevin]

Originally Posted by rick-k

Instead of this line at the beginning of your Perl scripts:
#!/usr/local/bin/perl

use:
#!/usr/bin/perl

The first generates errors.

To be fair, that is the correct path on our servers too we just have a symlink to make both work.