Re: bypassing the site-wide error handler
Thanks Dave, Rodney. That really helped. It turned out our issue was the same cfscript in the application's header and the sitewide error handler's header. When the second instance of cfscript tried to run, it broke the error handler, thus presenting the raw error to the user. best, Chris On Mon, Dec 8, 2014 at 10:02 PM, Rodney Enke renk...@gmail.com wrote: The site wide error handler will not run if there is a local error handler, such as CFTRY/CFCATCH or CFERROR, unless the CFTRY/CFCATCH block rethrows the error. - Rodney On Mon, Dec 8, 2014 at 8:52 PM, Dave Watts dwa...@figleaf.com wrote: Hi, when can an application bypass the CF v9 site-wide error handler? We host an app, that uses cftry/catch, but that appears to not handle the errors correctly. The errors do not trigger the site-wide error handler, and the errors are displayed to the users. The site-wide error handler works fine for other applications, and testing. I don't think the application can, by itself, bypass the site-wide error handler. I'd take a look at the code in the site-wide error handler to see if there's anything in there that would prevent it from doing anything when an error occurs. You might also look at how you're using CFTRY/CFCATCH - maybe you are catching the error after all, and your error trapping code doesn't do anything useful. Finally, the site-wide error handler will only catch run-time exceptions, I think. I could be wrong about this, as I haven't worked with the site-wide error handler in a while, but if this is the case and you have a compile-time error in your code, it's going to be displayed. This is something that used to be handled with the CFERROR tag (type=request), but you really just shouldn't have any compile-time errors anyway. Dave Watts, CTO, Fig Leaf Software 1-202-527-9569 http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Service-Disabled Veteran-Owned Small Business (SDVOSB) on GSA Schedule, and provides the highest caliber vendor- authorized instruction at our training centers, online, or onsite. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359797 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
bypassing the site-wide error handler
Hi, when can an application bypass the CF v9 site-wide error handler? We host an app, that uses cftry/catch, but that appears to not handle the errors correctly. The errors do not trigger the site-wide error handler, and the errors are displayed to the users. The site-wide error handler works fine for other applications, and testing. Thanks for any insight! Chris ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359774 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: bypassing the site-wide error handler
Hi, when can an application bypass the CF v9 site-wide error handler? We host an app, that uses cftry/catch, but that appears to not handle the errors correctly. The errors do not trigger the site-wide error handler, and the errors are displayed to the users. The site-wide error handler works fine for other applications, and testing. I don't think the application can, by itself, bypass the site-wide error handler. I'd take a look at the code in the site-wide error handler to see if there's anything in there that would prevent it from doing anything when an error occurs. You might also look at how you're using CFTRY/CFCATCH - maybe you are catching the error after all, and your error trapping code doesn't do anything useful. Finally, the site-wide error handler will only catch run-time exceptions, I think. I could be wrong about this, as I haven't worked with the site-wide error handler in a while, but if this is the case and you have a compile-time error in your code, it's going to be displayed. This is something that used to be handled with the CFERROR tag (type=request), but you really just shouldn't have any compile-time errors anyway. Dave Watts, CTO, Fig Leaf Software 1-202-527-9569 http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Service-Disabled Veteran-Owned Small Business (SDVOSB) on GSA Schedule, and provides the highest caliber vendor- authorized instruction at our training centers, online, or onsite. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359775 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
Re: bypassing the site-wide error handler
The site wide error handler will not run if there is a local error handler, such as CFTRY/CFCATCH or CFERROR, unless the CFTRY/CFCATCH block rethrows the error. - Rodney On Mon, Dec 8, 2014 at 8:52 PM, Dave Watts dwa...@figleaf.com wrote: Hi, when can an application bypass the CF v9 site-wide error handler? We host an app, that uses cftry/catch, but that appears to not handle the errors correctly. The errors do not trigger the site-wide error handler, and the errors are displayed to the users. The site-wide error handler works fine for other applications, and testing. I don't think the application can, by itself, bypass the site-wide error handler. I'd take a look at the code in the site-wide error handler to see if there's anything in there that would prevent it from doing anything when an error occurs. You might also look at how you're using CFTRY/CFCATCH - maybe you are catching the error after all, and your error trapping code doesn't do anything useful. Finally, the site-wide error handler will only catch run-time exceptions, I think. I could be wrong about this, as I haven't worked with the site-wide error handler in a while, but if this is the case and you have a compile-time error in your code, it's going to be displayed. This is something that used to be handled with the CFERROR tag (type=request), but you really just shouldn't have any compile-time errors anyway. Dave Watts, CTO, Fig Leaf Software 1-202-527-9569 http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Service-Disabled Veteran-Owned Small Business (SDVOSB) on GSA Schedule, and provides the highest caliber vendor- authorized instruction at our training centers, online, or onsite. ~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359776 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
