That's the idea 8^). Obviously, test it before deployment to make sure it works as expected... blah blah.
-- Mosh Teitelbaum evoch, LLC Tel: (301) 625-9191 Fax: (301) 933-3651 Email: [EMAIL PROTECTED] WWW: http://www.evoch.com/ > -----Original Message----- > From: Rick Faircloth [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 17, 2002 10:42 PM > To: CF-Talk > Subject: RE: cferror > > > So, that's why Scott uses Exception to catch the error... > it catches everything and allows an email to be sent to the specified > address. > > Should Exception have any problems, Request would then kick in and > simply return the error message to the user, as would normally happen. > > Right? > > I think I'll set this up for my apps, too. I run my own server and would > like > to know quickly when errors are occuring and getting the emails would > be quicker notification, even though my server and monitor sit > right beside > my development pc. > > Any problems with this scenario? > > Rick > > > -----Original Message----- > From: Mosh Teitelbaum [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 17, 2002 6:03 PM > To: CF-Talk > Subject: RE: cferror > > > REQUEST is essentially a (near) catch-all error that is defined > as any error > that occurs server-side other than a validation error. EXCEPTION > is pretty > much like a top-level CFCATCH in that it catches any uncaught > exception. In > fact, (if you specify EXCEPTION="Any" or don't specify an EXCEPTION value) > it does pretty much the same thing as REQUEST except that it allows you to > use CF functionality in your error template. However, you should > still use > a REQUEST CFERROR because, if the CF code in your EXCEPTION handler throws > an exception, it can only be caught by REQUEST. > > -- > Mosh Teitelbaum > evoch, LLC > Tel: (301) 625-9191 > Fax: (301) 933-3651 > Email: [EMAIL PROTECTED] > WWW: http://www.evoch.com/ > > > > -----Original Message----- > > From: Rick Faircloth [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, December 17, 2002 5:23 PM > > To: CF-Talk > > Subject: RE: cferror > > > > > > I guess the error type "request" is defined by an error occuring > > when a page > > is requested, but fails... > > How is the "exception" error defined? > > > > Rick > > > > > > -----Original Message----- > > From: Scott Brady [mailto:[EMAIL PROTECTED]] > > Sent: Monday, December 16, 2002 5:26 PM > > To: CF-Talk > > Subject: RE: cferror > > > > > > >One thing to watch out for, though - if your error page itself > > generates an > > >error, odd things might happen. I suspect that's the reason that > > you can't > > >use CFML tags and functions in a Request error page. If your site-wide > > error > > >handler page generates an error, the user will see the default > raw error > > >message page instead. > > > > We get around that this way: > > > > At the bottom of Application.cfm, we have two cferror tags. The > > first one is > > type="Exception" which allows us to e-mail the admin and provide error > > diagnostic info. However, if that generates an error (for some > > reason), the > > second cferror tag is type="request" which basically puts up a page that > > says "An error has occurred." without the CF error diagnostic stuff. > > > > Scott > > -------------------------------- > > Scott Brady > > http://www.scottbrady.net/ > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting.
