I think valdez
is likely to be right - unless it's something even simpler, like the filepath you specified is wrong or incomplete. My only suggestion is that if you are looking in the error log for your error messages, then you could save yourself some trouble by putting
use CGI::Carp qw(fatalsToBrowser warningsToBrowser);
near the top of your code during development - it'll chuck your fatal errors (and your warnings if you put -w
at the end of your shebang line) onto the browser where you can see 'em in real time.
§ George Sherston
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||