cferror

Displays a custom HTML page when an error occurs. This lets you maintain a consistent look and feel among an application's functional and error pages.

Exception handling tags, Extensibility tags, Application framework tags

<cferror 
   type = "a type"
   template = "template_path"
   mailTo = "email_address"
   exception = "exception_type">

cfrethrow, cfthrow, cftry

ColdFusion MX: Deprecated the monitor option of the exception attribute. It might not work, and might cause an error, in later releases.

Attribute	Req/Opt	Default	Description
type	Required		Type of error that the custom error page handles. The type also determines how ColdFusion handles the error page. For more information, see Specifying a custom error page in Developing ColdFusion MX Applications. exception: a exception of the type specified by the `exception` attribute. validation: errors recognized by sever-side type validation. request: any encountered error.
template	Required		Relative path to the custom error page. (A ColdFusion page was formerly called a template.)
mailTo	Optional		An E-mail address. This attribute is available on the error page as the variable `error.mailto`. ColdFusion does not automatically send anything to this address.
exception	Optional	Any	Type of exception that the tag handles: application: application exceptions database: database exceptions template: ColdFusion page exceptions security: security exceptions object: object exceptions missingInclude: missing include file exceptions expression: expression exceptions lock: lock exceptions custom_type: developer-defined exceptions, defined in the `cfthrow` tag any: all exception types For more information on exception types, see cftry

Use this tag to provide custom error messages for pages in an application. You generally embed this tag in the Application.cfm file. For more information, see Handling Errors in Developing ColdFusion MX Applications.

To ensure that error pages display successfully, avoid using the cfencode tag to encode pages that include the cferror tag.

Page Types

The following table describes the types of errors you can specify and code you can use on the pages that handle these error type.

Page type Description Use

Page type	Description	Use
Exception	Dynamically invoked by the CFML language processor when it detects an unhandled exception condition. Uses the full range of CFML tags. Error variables must be in `cfoutput` tags.	Can handle specific exception types or display general information for exceptions.
Request	Includes the error variables described in the Error Variables section. Cannot include CFML tags, but you can display values of the error variables by enclosing them in number signs (#), as in #error.MailTo#.	Use as a backup error handler to other error handling methods, including exception type.
Validation	Handles data input validation errors that occur when submitting a form that uses hidden form-field validation. Cannot include CFML tags, but you can display values of the error variables by enclosing them in number signs (#), as in #Error.InvalidFields#. You must specify the validation error handler in the Application.cfm file.	Handles hidden form-field style validation errors only.

Exception

Dynamically invoked by the CFML language processor when it detects an unhandled exception condition.

Uses the full range of CFML tags. Error variables must be in cfoutput tags.

Can handle specific exception types or display general information for exceptions.

Request

Includes the error variables described in the Error Variables section.

Cannot include CFML tags, but you can display values of the error variables by enclosing them in number signs (#), as in #error.MailTo#.

Use as a backup error handler to other error handling methods, including exception type.

Validation

Handles data input validation errors that occur when submitting a form that uses hidden form-field validation.

Cannot include CFML tags, but you can display values of the error variables by enclosing them in number signs (#), as in #Error.InvalidFields#.

You must specify the validation error handler in the Application.cfm file.

Handles hidden form-field style validation errors only.

Error variables

The exception-handling page specified in the cferror tag template attribute contains one or more error variables. ColdFusion substitutes the value of the error variable when an error displays.

The following table lists error variables:

Page type	Error variable	Description
Validation only	error.validationHeader	Validation message header text.
	error.invalidFields	Unordered list of validation errors.
	error.validationFooter	Validation message footer text.
Request and Exception	error.diagnostics	Detailed error diagnostics from ColdFusion MX.
	error.mailTo	E-mail address (same as value in `cferror.MailTo`).
	error.dateTime	Date and time when error occurred.
	error.browser	Browser that was running when error occurred.
	error.remoteAddress	IP address of remote client.
	error.HTTPReferer	Page from which client accessed link to page where error occurred.
	error.template	Page executing when error occurred.
	error.generatedContent	The content generated by the page up to the point where the error occurred.
	error.queryString	URL query string of client's request.
Exception only	error.messge	Error message associated with the exception.
	error.rootCause	Java servlet exception reported by the JVM as the cause of the "root cause" of the exception. This variable is a Java object.
	error.tagContext	Array of structures containing information for each tag in the tag stack. The tag stack consists of each tag that is currently open.
	error.type	Exception type.

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."

Note: If type = "exception" you can substitute the prefix cferror for Error; for example, cferror.diagnostics, cferror.mailTo, or cferror.dateTime.

<h3>cferror Example</h3>
<p>cferror lets you display custom HTML pages when errors occur. This lets you
maintain a consistent look and feel within the application even when
errors occur. No CFML can be displayed in the pages, except specialized
error variables.
<p>cftry/cfcatch is a more interactive way to handle CF errors within a CF page
than cferror, but cferror is a good safeguard against general errors.
<p>You can also use cferror within Application.cfm to specify error 
handling responsibilities for an entire application.
<!--- Example of cferror call within a page --->
<cferror type = "REQUEST"
    template = "request_err.cfm"
    mailTo = "[email protected]">

<!--- Example of the page to handle this error --->
<html>
<head>
   <title>We're sorry -- An Error Occurred</title>
</head>   
<body>
   <h2>We're sorry -- An Error Occurred</h2>
   <p>
      If you continue to have this problem, please contact #error.mailTo#
      with the following information:</p>
   <p>
<ul>
   <li><b>Your Location:</b> #error.remoteAddress#
   <li><b>Your Browser:</b> #error.browser#
   <li><b>Date and Time the Error Occurred:</b> #error.dateTime#
   <li><b>Page You Came From:</b> #error.HTTPReferer#
   <li><b>Message Content</b>:
    <p>#error.diagnostics#</p>
</ul>

cferror

Page Types

Error variables

View comments on LiveDocs