Nov 2, 2008, 10:28 PM
Post #10 of 13
thanks for the thoughtful followup
Re: [FishMonger] first perl form, 6hrs no luck yet
[In reply to]
so good news and bad news, i got another script working, suggested, then modified, from the active perl documentation, i got it working with a shebang line first, then it also worked with out the shebang line using the scriptInterpreterSource directive, so that seems better than the shebang line, in case the perl install ever changes or is in a different location when moving to a different server. in the apache writeup about it, it talked about where and what the registry entry was, but searching my registry i didn't see any entries for perl in the section they talked about, so thats strange. the new working script is:
# previous line added to support Apache 1/2
# please adjust to your own Perl path!
use CGI qw(:standard); (i changed this from above for the param function)
my $page = new CGI;
my $msg = "Hello from ActivePerl CGI!";
# my $data = 'hard coded';
my $data = param('sample') || '<i>(No input)</i>';
# print header and start the markup output
print $page->header( "text/html" ),$page->start_html( $msg );
print "<p>You typed: $data</p>";
# end code
the difference that i can see from the scripts i was trying is the: use strict; , the 'my' with variables, and the print $page-> syntax, at some point i would like see which one of those made the difference.
the bad news is all the unknowns from above and i still can't get the original target script, ubr_upload.pl, from the open source uber upload application, working. it is a complex script and application. i don't expect to solve that here, unless somebody has a suggestion for the firefox message it gives me: 'Firefox doesn't know how to open this address, because the protocol (c) isn't associated with any programs'. From what i've read so far the '(c)' indicates a path problem, and i've quadrupled checked all the paths and think they be right.
so thanks for all your help, its been a good education here.