Correct, compile-time errors aren't handled by CFERROR, which is a runtime construct. The assumption being that you'll never have code with compiler errors in production. So try <cfset dx = lskdjf /> or something, and you should see the CFERROR-defined message, not the raw CF one.
cheers, barneyb On 8/10/05, Ali Awan <[EMAIL PROTECTED]> wrote: > Thanks Barney, > > I forgot to mention that this is for a server running CF5. > I'm testing out CFError by deliberately putting an error in one of my pages > by not closing the CFSET tag > Example: <cfset t > > But it's still displaying the Coldfusion generated error in plain view. It > does not seem to be executing the CFError tag. > I'm not really sure what to specify as the Type attribute if I want to handle > all errors. I tried putting in Type="Exception" but I still see the error, > rather than the template. > > Ali > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:214483 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
