As much as like the concept of the bubble-up error handling. I
personally handle errors differently. I attempt to catch EVERY error
ever generated by CF and email me all the debugging info. While giving
the user a standard "uh oh" message.
It's a pain in the ass when you first launch, but you'll fix most of
your errors within your first day. Then you don't have to worry about
your error handler not working correctly.
Steve
Gary Morin wrote:
>
> Hi All
>
> I'm just about to start implementing error handling in XFB application, I
> will probably implement code similar to Hal Helms nested error handling
> code.
>
> Often errors are generated/captured in act_ pages, from the user perspective
> a polite message informing him of the error and requesting to do the
> appropriate action to correct the problem, this action may be refreshing the
> page, or doing a login etc. Cftry and Cfcatch will be used to handle the
> errors
>
> My question is what is the excepted way to notify the problem to the user?
> In some examples, including Hal's, HTML messages are placed directly in the
> act file or even in the index.cfm, if the nested error handling code is
> used. Or should I use an 'Error fuse' to display and error message and use
> a XFA to return the user to the appropriate position to continue( this would
> also require all variables to be passed through the error handling code).
>
> So how do others handle simple errors and informing users?
>
> Cheers
>
> Gary
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
