Hello,
We use an eval statement in our instance scripts and then pass the string
(the error string from the eval{ }) to another object which outputs the
proper error message. The object which is passed the error message is
defined in the instance script, which is generated from the
CGI::Application's configuration file.
The object, our "error handler" can do whatever it likes. If it is a
ErrorHandlers::Developer, it prints everything. If it is
ErrorHandlers::Security it prints a terse message. If
ErrorHandlers::Production, it prints something friendly.
I have attached a proof-of-concept, which shows the basic idea. It contains
specific code for our session, configuration, security, and instance script
generation stuff, but the idea is relatively clear.
Thanks,
-- Cory
> -----Original Message-----
> From: Kenny Pyatt [mailto:suppressed
> Sent: Monday, February 03, 2003 10:54 AM
> To: suppressed
> Subject: [cgiapp] Customized Error Screens
>
>
> List Folk,
>
> What is the 'best' way to create a customized (read: attractive and
> informative) error screen while using CGI::App with
> HTML::Template and DBI.
> Each generate thier own error messages. We would like to make
> two different
> sets of customized error screens. One set for development and
> another for live
> sites. We have managed to do this in some specific error cases
> but not all.
> Any ideas?
>
>
> Sincerely,
> Kenny Pyatt
> President
> Venzia
> http://www.venzia.com
>
>
> ---------------------------------------------------------------------
> Web Archive: http://www.mail-archive.com/suppressed/
> To unsubscribe, e-mail: suppressed
> For additional commands, e-mail: suppressed
>
Attachment:
login.pl
Description: Perl program
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.