Whenever I am troubleshooting a web problem, I keep a separate terminal window open and 'tail -f error.log' for the apache error log. It usually makes quick work of tracking down where a problem lies, especially since most browsers aren't giving useful error messages directly to the browser.

Also, it's a great help if you post some code (using the <code> tag) so we can better assist in finding the problem. If the code isn't too long, I'd recommend posting the entire thing, so someone can just copy/paste the entire script into their own system and try to run it (obviously having uncommon dependencies may hinder this) but it's good to get an overall idea of what you're trying to do, and what is actually happening.

In reply to Re: PERL Changes by sierpinski
in thread PERL Changes by djpekingman

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.