This would work, as would a cferror tag in the Application.cfm file, if the error made it that far. I've noticed that some cfcatch blocks in the core code have there contents commented, making it difficult to track down bugs.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Cornilliac Sent: Thursday, April 29, 2004 5:01 PM To: FarCry Developers Subject: [farcry-dev] RE: Error Messages for Debugging > What I'm more concerned about is when an end user encounters an error. I > know I can check the CF log files, but it would be nice to get an e-mail > when something goes wrong. You could simply put the include in index.cfm in a try/catch block like so: <cftry> <cfinclude template="/farcry/#application.applicationname#/ui/index.cfm"> <cfcatch> <!---Send email and handle exception ---> </cfcatch> </cftry> --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
