Feature
Toward Better Error Handling
We've all seen it: the dreaded 'Error Occurred While Processing Request,' which is the headline above a normal CF error message. As developers, of course, we relish the detail it offers: the CF error message, the line number and actual line of code in error, the name and path of the template in which it occurred, and so on. But is this the best thing to show our end users?
Reader Feedback : Page 1 of 1