Is there any way to programmatically ignore the

Application.cfc

onError

function? I have an

isProduction()

function and was hoping I could only enable the error-trapping and re-routing functionality conditionally based on that. It doesn't quite seem to work that way when NOT in prod. It just swallows up errors and doesn't display anything on the page, unless the function is commented out.

I've never tried this so it probably doesn't work, but what if you did

onError(any exception) {
    if( !isProduction() ) {
      rethrow;
    }
}

In reality, what I have is more like:

onError(any exception) {
    log(exception);
    if( !isProduction() ) {
        writeDump(exception);
    }
}

I'll give that a shot and let ya know!

You could try aborting after the writeDump. I think that works in a tag based application.cfc.

Mine is cfscript based so unfortunately the dump after didn't work 😞

It doesn't quite seem to work that way when NOT in prod.

It's pretty hard to comment on why your code is not working the way you want if we're just left to guess what it is 😉 Also:

Yeah, it doesn't work.

What does "doesn't work" mean in this context? What does it do? And how does that vary from what you expected?

What adam's got was going to be my second guess, but the docs said that was java exceptions, and I wasn't sure if CF exceptions were also java exceptions or not. As for what my code does -- technically I'm not using a writeDump. I'm parsing the exception to json for nicer logging, passing that to a View.cfc, and writeOutput-ting the html that the view generates. And it displays a page when there's an error. I believe writeDump isn't doing anything substantially different from that, so I figured it would output the dump of the exception in place of the blank page you're getting now.

Gentlemen, thank you for your assistance. The writeDump ended up working on the blank error page. It turns out I had an error when trying to log the exception.

Make sure to have your code in the

onError

handler itself `try`/`catch`ed with just a final fallback to just a

writeLog

entry, and a

rethrow

Good call. I was meaning to find the correct log function to put in my catch, but thanks to you it just fell in my lap. Appreciate it 🙂

This is what I have in mine and it works pretty good