http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-24T21:39:13 en-us http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#50266 An additional note on CFError. Despite information above to the contrary, the cferror tag does not catch all CF errors, regardless of the TYPE attribute that you specify. For example, if you leave off the closing parenthesis in the following tag: #left(sometext, 20#, the CFError will NOT trigger. However, if you properly form the tag but pass an invalid variable (for example passing a misspelling of #left(smoetext, 20)#, the error template will trigger fine. For CFError to process, there can not be any malformed CF, just malformed variables, truncation, etc. thekat 0 0 2006-06-29T23:32:34 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#39931 "To ensure that error pages display successfully, avoid using the cfencode tag to encode pages that include the cferror tag."<br /><br />cfencode is not a tag, it is an application used to encode a cfml file gyzer 0 0 2005-09-26T00:37:40 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#36127 If you're asking how to display an error template on a 404, then I think that either the Site-wide error handler or errorurl property in the web server connector are what you need. For more information on the site-wide error handler, see the CF Administrator online help; for more information on the Web server connector, see: http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/websera8.htm. jrunrandy 1 1 2005-06-29T12:35:19 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#35698 It's unclear whether using CFERROR is the same as setting a site-wide error template in the CF administrator, if it is different, or just when/why you'd use one over the other. csteinola 0 0 2005-06-17T12:28:09 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#34364 What about page not found error?<br /><br />Error Occurred While Processing Request <br />File not found: /property/system/123.cfm walkman 0 0 2005-06-02T16:07:35 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#25941 Has anyone encounter a problem of filtering custom exception types in cferror pages? When I use any unrecognized or custom exception types to filter, cferror tag lets them IN instead of OUT of my error handling page. Can anyone tell me a solutiont to this?? Thanks! 0 0 2004-12-29T09:27:48 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#23878 You can use <cfdump var=#error#> to get all the information you want to get. And you will find out the structure of variable Error. Dogfish88 0 0 2004-11-12T17:57:14 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#23720 jdugandzic: I would like to know how did you do it. I have the same issue and for some reason cannot access Error.sql when i use my own error handling page specified by <cferror type="exception" ...><br /><br />The strange thing is that when one uses default Site-wide error handling page (i.e. without specifying <cferror>) error.sql data is available. I've investigated this and have discovered when a database exception is handled by the default error handler (located for me in C:\CFusionMX\wwwroot\WEB-INF\exception\coldfusion\runtime\ DatabaseException.cfm) the Error object has the following keys:<br /><br />Sql,SQLState,queryError,RootCause,where,StackTrace,Detail,NativeErrorCode,Message,DataSource,ErrorCode,Type,TagContext<br />However, that exact same exception when i use my own error page -- as specified by cferror - the error object is missing sql data and has only the following keys:<br /><br />GeneratedContent,Mailto,RootCause,RemoteAddress,StackTrace,QueryString,HTTPReferer,Template,Message,Diagnostics,DateTime,Browser,Type,TagContext<br /><br />This is quite an unexpected behavior and it should at least be documented if not fixed.<br /><br />If someone figures out how to get Error.sql please let me know [dupublic(no/spam)@twcny.rr.com] dorange 0 0 2004-11-09T18:02:30 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#23549 Nevermind, I found that this information is partially correct. The cfcatch variables are not available, but the sql stuff is available buried deep in the cferror structure. thanks for lots of documentation on this macromedia!!!!! :( jdugandzic 0 0 2004-11-05T14:46:10 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#23548 I am trying to add some additional debugging info to my cferror pages. I need to see the sql statement that caused an error. Macromedia's docs say that 'In exception error handling pages, you can access the error variables that are also available to the cfcatch tag. See cfcatch for a description of these variables. To use these variables, prefix them with "cferror." '<br /><br />This works in theory, but not for real. If I use #cferror.sql# , the error-handling page bombs out and reverts back to the original sql error and doesn't actually process my error handling. Has anyone had experience with this? Has anyone ever been able to have their error handling page show the sql statement that caused the error? This would help me greatly. I have just about every other piece of information to help me debug except this one, and it's a big one!<br /><br />Thanks jdugandzic 0 0 2004-11-05T14:24:11 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#22061 Use the error.template variable. murat 0 0 2004-10-07T02:41:13 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#21198 Typo: "sever-side type validation" should be server... parrot person 0 0 2004-09-10T08:03:56 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#15403 Typo?: error.messge profit11 0 0 2004-05-25T16:21:20 http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-p24.htm#11865 We are working to improve the examples in the ColdFusion reference pages. We propose to replace the current example on this page with the the following example. If you have any comments on this example, add them to this page.<br /><br /><h3>cferror Example</h3><br /><p>cferror lets you display custom HTML pages when errors occur. This lets youmaintain a consistent look and feel within the application even whenerrors occur. No CFML can be displayed in the pages, except specializederror variables.<br /><p>cftry/cfcatch is a more interactive way to handle CF errors within a CF pagethan cferror, but cferror is a good safeguard against general errors.<br /><p>You can also use cferror within Application.cfm to specify error handling responsibilities for an entire application.<br /><!--- Example of cferror call within a page ---><br /><cferror type = "REQUEST"<br /> template = "request_err.cfm"<br /> mailTo = "admin@mywebsite.com"><br /><!--- This query calls a non-existant datasource, triggering an error to be handled---><br /><cfquery name="testQuery" datasource="doesNotExist"><br /> select * from nothing<br /></cfquery><br /><br /><!--- Example of the page to handle this error ---><br /><html><br /><head><br /> <title>We're sorry -- An Error Occurred</title><br /></head> <br /><body><br /> <h2>We're sorry -- An Error Occurred</h2><br /> <p><br /> If you continue to have this problem, please contact #error.mailTo#<br /> with the following information:</p><br /> <p><br /><ul><br /> <li><b>Your Location:</b> #error.remoteAddress#<br /> <li><b>Your Browser:</b> #error.browser#<br /> <li><b>Date and Time the Error Occurred:</b> #error.dateTime#<br /> <li><b>Page You Came From:</b> #error.HTTPReferer#<br /> <li><b>Message Content</b>:<br /> <p>#error.diagnostics#</p><br /></ul> wlee 0 0 2004-03-26T08:32:38