Hello all,
ok, if I have this right,
cferror lets me use a custom template instead of the default CF error output, in which I can use all the nice 'ERROR. variables', but CF will not parse coldfusion tags in this template.
ok ... understandable
but if I use cftry/cfcatch I can do whatever I want (cfmail,cffile, etc.), but now I don't have any goodies! (error.diagnostics, etc.), and not only that, CF makes no entry in the application.log!
Am I missing something? Is there some sort of happy medium?
For a particular template, I need 2 things :
1. notification of errors (via cfmail or cffile)
2. description of errors (via anything)
(to my knowledge, this can only be accomplished by constantly scanning the application log)
Is there a way to get detailed error diagnostics from the system using cfcatch?
two clumps short a full head
-Marc
ok, if I have this right,
cferror lets me use a custom template instead of the default CF error output, in which I can use all the nice 'ERROR. variables', but CF will not parse coldfusion tags in this template.
ok ... understandable
but if I use cftry/cfcatch I can do whatever I want (cfmail,cffile, etc.), but now I don't have any goodies! (error.diagnostics, etc.), and not only that, CF makes no entry in the application.log!
Am I missing something? Is there some sort of happy medium?
For a particular template, I need 2 things :
1. notification of errors (via cfmail or cffile)
2. description of errors (via anything)
(to my knowledge, this can only be accomplished by constantly scanning the application log)
Is there a way to get detailed error diagnostics from the system using cfcatch?
two clumps short a full head
-Marc