in reply to (Ovid) Re(3): uninitialized values for arrays suddenly appear
in thread uninitialized values for arrays suddenly appear

Could someone explain to me how to track errors from a script on my server? The errors these scripts produce in local tests have to do with expecting form data and searching directories on my server. I assume I could rewrite the var values to search my desktop but I am entirely unsure if that would suffice. I believe I need to test in situ on my server, no?
TIA
jg
  • Comment on Re: (Ovid) Re(3): uninitialized values for arrays suddenly appear

Replies are listed 'Best First'.
Re: Re: (Ovid) Re(3): uninitialized values for arrays suddenly appear
by runrig (Abbot) on Sep 08, 2001 at 01:59 UTC
    If you're on a different machine and testing from the command line, then sure you'd have to create corresponding directories, and it may be worthwhile. You can supply the form parameters in several ways, IMO its easiest to put them in a file (makes them easy to change later) like this (often you can just cut n paste from the URL browser window):
    param1=value1 param2=value2 etc=etc
    You can even leave them as the actual query string joined by '&' or ';', but to me its easier to edit when you separate them as above. Then you run your script with the CGI debug parameter on with this file as STDIN:
    ./my_cgi_script <my_parameters
    To me its easier to get it working from the command line first, than constantly having to check the web logs (yes you can use FatalsToBrowser, but it doesn't help if your script dies before headers get output).