Skip to main content
Participant
July 17, 2009
Answered

My sitewide error handler doesn't get called (i am new)

  • July 17, 2009
  • 2 replies
  • 711 views

I have a sitewider error handler defined in the Admin panel, and i am pretty sure it sees it. If i change the name to a non-existent file, i get an error. The problem is that that page never gets called, no matter what application i try trigger an error from.

I just have a file with a single line of code in it <cfoutput>#xfhdshsdhj#</cfoutput> and that triggers an error. But it displays the ugly default message, rather them my custom error handler.

Is there anything i need to set in the application?

I would appreciate any help, i am very new to ColdFusion.

    This topic has been closed for replies.
    Correct answer charmed0rz

    I am new also to coldfusion so i might be wrong here. I've never used the cfadmin for sitewide error pages, so im not sure how to help you there if you must do it that way - but if you wanted to try something different i think <cftry> and <cfcatch> do the same thing and i hear it works fine.

    2 replies

    Participating Frequently
    July 17, 2009

    Make sure that you don't have an error within your site-wide error

    handler. Start just with some text and then progressively add your CF

    code.

    Mack

    Participant
    July 17, 2009

    Sorry, i meant to mark you answer as correct, and the other as helpful.

    When i just put some text into my error handler file, it loaded, so there's probably a problem with the ColdFusion code.

    How can i change your post to be the correct answer?

    Participating Frequently
    July 17, 2009

    I don't know if you can do that, I don't use the forums web interface.

    But I think your comment is enough for others that will have this or a

    similar problem in the future.

    Mack

    charmed0rzCorrect answer
    Participant
    July 17, 2009

    I am new also to coldfusion so i might be wrong here. I've never used the cfadmin for sitewide error pages, so im not sure how to help you there if you must do it that way - but if you wanted to try something different i think <cftry> and <cfcatch> do the same thing and i hear it works fine.