But what about suggestions a) and b)?
Perhaps my "should
be helpful" was a little too casual. Those are not
throw-away suggestions. They are likely the two most
common and effective
strategies for solving the kind of problem
you describe. If you peruse the archives here at Perl
Monks you will see
them recommended again and again.
They will likely lead you to a solution to your current
problem. And checking those two things should become
second nature for you any time you have a problem of this
sort because they are such reliable strategies.
In
particular, find out where your server error log is and
befriend it. It is one of your most reliable resources
for debugging CGI.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.