sysrpl said:figuerres said:*snip*
Actually I was trying to create a universal "catch all" error screen with detailed information, but formatted in a way/styling of my own design. Thanks for the replies. I'll keep looking around for how to get this done.
do you really want your visitors to know about your null/object not found exceptions or is this for debugging?
in my humble opinion i think it's better to log those exceptions and direct to a *fairly* generic error page, meaning you could catch/redirect to a certain generic error page based on the context the error was created in. then you could email the exception to dev from the log or database if you choose to store it there (i prefer this method because i can also get additional details about the session/context, not necessarily included in the stack trace and report off of it to detect patterns).