Well, while you can't edit the template, you can certainly just point to a new one in the field of the CF Admin. :-) As I tried to clarify, it's just that the "Secure profile" pre-fills that field with a pointer to this newly provided template by default (so that there is at least SOME page that intercepts errors, versus the more traditional "standard CF error page" output). But yes, you can certainly still change the Admin to point to a different file (or even remove it leaving none, which then causes CF to show what it always showed).
Some would argue that even with "robust exception handling" turned off (and not exposing details like the line number, CFML code in error, etc.) that the traditional error output (for unhandled errors) was giving too much info, thus the new default "generic" template. That's my understanding of things, at least. I was just an observer in all this throughout the prerelease, not an influencer in any way. :-) Hope that helps. /charlie From: cfaussie@googlegroups.com [mailto:cfaussie@googlegroups.com] On Behalf Of Steve Onnis Sent: Monday, September 10, 2012 8:28 PM To: cfaussie@googlegroups.com Subject: RE: [cfaussie] Coldfusion 10 debug nifo covered by black strip Charlie Do you know if you can change it back to the standard error template? I tried to edit the template itself but it is an encrypted template Steve From: Charlie Arehart [mailto:charlie_li...@carehart.org] Sent: Monday, 10 September 2012 11:27 PM To: cfaussie@googlegroups.com Subject: RE: [cfaussie] Coldfusion 10 debug nifo covered by black strip Folks/Steve, this odd-looking error page is indeed a feature of CF10-that is, if you have enabled the new "secure profile" feature during installation, which Steve must have done (and Dale and others on CF10 not seeing it, had not). So this odd error page Steve's seeing is the result of the HTML generated in a page that's defined as the sitewide error handler (the file pointed to in the corresponding field of the CF Admin server settings page). When the "secure profile" feature is selected, that sitewide error field is prepopulated with a new pre-written (bland) error CFM page (otherwise, the default is for that sitewide error handler field to be blank on install). So CF10 users with the secure profile enabled will see that "new" error page on any CF error that is otherwise not handled in their code. Traditionally, any error in CF that's not handled would get the "good old CF error page" (which showed details or not depending on the "robust exception handling" setting). With the new "secure profile", you see this generic page with little info. It's all about being more secure, of course. :-) But I'm sure many people will be caught out by this for some months/years to come, as people get used to it. As we saw here, even those "also on CF10" won't see it, unless they have used the "secure profile" feature-and only then if they have otherwise unhandled errors. Hope that helps. /charlie -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
