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);
print $cgi->header;
warningsToBrowser(1);
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
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|