Dear Gentle Monk,
First off let me comment that one of the tools that I
use all the time when debugging code prior to its
release into production is:
The information that will emit to your browser when something terrible goes wrong can often save you lots of aggravation later on.use CGI::Carp qw/ fatalsToBrowser /;
It should be stressed, however, that you would modify the CGI::Carp invocation prior to release to production to remove the qw/ fatalsToBrowser / line and let fatal errors got to you server's logs instead.
If you haven't read it already check out CGI Help Guide as it has some good dope in it as well as far as troubleshooting errant CGI scripts.
Offhand from what little code you have provided for us to look at I'd say it was a pathing issue. I am particularly suspicious of the line:
Relative paths can trip you up time and time again.@files = <../data/texts/*.txt>;
| Peter L. Berghold -- Unix Professional Peter at Berghold dot Net | |
| Dog trainer, dog agility exhibitor, brewer of fine Belgian style ales. Happiness is a warm, tired, contented dog curled up at your side and a good Belgian ale in your chalice. | |
In reply to Re: 2 perl cgi little problems!
by blue_cowdawg
in thread 2 perl cgi little problems!
by Nik
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |