Create an error routine to execute when something goes wrong, present a happy screen to the users letting them know that some sort of non problematic (don't panic!) problem has occured and to contact X if they desire.

then internally, log what really happened (the web logs might suffice instead), or perhaps shoot an email to yourself with the real error so you can dig in and fix it.

for instance, if we can't connect to the database, rather than present the ORA error messages, we just post a "system down" message that assures the users that it's temporary, and provides information for them to contact support.

good luck!

In reply to Re: DIE or Fatals cause Redirect? by wardk
in thread DIE or Fatals cause Redirect? by c

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.