CFError error in MX7?

[Steve Sommers]

Anyone know what would cause a cferror error template to not execute? By "not execute", I mean it is being called but the raw source of my error.cfm template is being sent as-is to the user -- no CF processing of the template.

I've commented out the entire template using <!--- ... --->, all that resulted in was a big comment being sent to the user. Very strange since I use cferror all the time in other applications.

[Steve Sommers]

Nevermind!

The type parameter was set to the default of REQUEST instead of EXCEPTION. I have no idea what REQUEST does, but based on the documentation I don't think sending the raw error template to the user was the intended functionality -- but I couold be wrong.

[BKBK · Accepted solution]

I have no idea what REQUEST does, but based on the documentation I don't think sending the raw error template to the user was the intended functionality -- but I couold be wrong.

It seems Coldfusion behaved as expected. The livedocs on cferror say two things. First, setting the type attribute to REQUEST is a general way to get cferror to run when there is "any encountered error". Secondly, if you set the type attribute to REQUEST or to VALIDATION, Coldfusion will not be able to process CFML tags. Makes sense, for the tags themselves could generate further errors.

[BKBK]

The first table in the document Specifying custom error messages with the cferror tag shows you the connection with the order in which Coldfusion processes a request-type error page.

[Steve Sommers]

Strange, I totally overlooked that table. The REQUEST function seems to be of marginal use but it is performing as intended. Thanks.