I am setting up the site-wide error handler in the CF Administrator. Its called whammo.cfm and its code is displayed in my original post on this.
Then there's the try/catch error handler. Thats oops.cfm and its declared at the bottom of /Application.cfm. It has the same code as whammo.cfm only it displays 'oops' instead of 'whammo' so I can be sure which template is firing. Then there's oops.html. Its just an html display page whose sole purpose is to tell me when what I'm seeing is coming from cferror. I'd do more of course in a real app and not a demo like this. > The thing with the errors that you are creating is that the two mods to the > code you made will have very different results and I don't think the error > handlers that are declared in your pages will ever fire under the > circumstances you are describing... I know. I'm not expecting them to. I'm expecting the site-wide error handler to pick it up. And it is. *But* its also exposing raw ColdFusion messages in one specific circumstance. *Thats* the deal here: Raw errors can make it to the screen even if you have a site-wide error handler, which is never supposed to happen. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:201957 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
