sulfericacid has asked for the wisdom of the Perl Monks concerning the following question:

Greetings everyone. I have a small perl script I tried to make but it doesn't work. My server doesn't allow fatals to browser. Can everyone go to www.spydersubmission.com/help/spyderrec.html ? One of the errors you will see is that FORM...is not written as $FORM. Don't worry about that. Thanks. Aaron

Replies are listed 'Best First'.
Re: Small Script
by chromatic (Archbishop) on Sep 29, 2001 at 10:02 UTC
    If I were you, I would install Perl on my personal machine and attempt to run the program there. IndigoPerl offers a distribution that runs on Windows and is bundled with the Apache web server.

    That said, there's something missing, namely, just about everything after the following line. English majors would call this a sentence fragment. Computers don't handle them well. I suppose they wouldn't read Hemingway.

    if ($adminnotify ==0){
    Figure out what goes after that, finish off the block, and it'll probably work better.

    It's hard to believe the server doesn't have CGI::Carp installed. If they're that many years behind on their version of Perl (eight, by my estimate), I'd be a little worried about their hosting capabilities. You might point out to them that the web has inline graphics now. :)

    (And, yes, you should be using strict and CGI. Then again, if your host hasn't figured out how to bang the rocks together, you're basically stuck with what you've got. Sorry.) ©

(tye)Re: Small Script
by tye (Sage) on Sep 29, 2001 at 10:41 UTC

    Well, until you figure out how to install CGI::Carp for your own use, you can see the follow-up to warningsToBrowser and just cut-n-paste that into your script.

    (Other excellent advice already given that I won't repeat.)

            - tye (but my friends call me "Tye")
Re: Small Script
by George_Sherston (Vicar) on Sep 29, 2001 at 10:37 UTC
    chromatic's right about running it locally. If for some unimaginable reason you can't, though, FTP into your web space and you're almost certain to find an error.log in a logs directory which will tell you more than you need to know.

    § George Sherston