Building the ultimate error email...

Question

Hello,
I'm using CFERROR to catch exceptions and generate an email
to myself. I
use to have all the basic #error.foo# variables in the email,
but I wanted
more. So I figured out how you can include most of what is in
the
classic.cfm template located in the web-inf/debug/ folder and
it will pretty
much send you all the normal debug output you get on a web
page with an
error and debug turned on.
Now for the catch, this works great for me with the exception
of the newer
CFMX style debug output you see at the top of your debug
output. This is
the area where CF actually will display several lines of code
in and around
the offending error. For some reason, this port of the debug
output is not
available in the classic.cfm file and I can't figure out
where to find it.
Has anyone done this? I'm actually very happy just getting
the classic CF 5
debut output, but I'd love even more to have the CFMX style
output as well.
Thanks so much!
...Brad
PS. I'm using CFMX 7.x on Linux.

Answer 1

Thanks Dave,
That works well except I can't seem to find the structure
that has the
information I am looking for. All the variables at already
nicely formatted
in "classic.cfm" but the newer MX style extra debug info you
get isn't in
that template and I'm still looking. Also, I'm trying to keep
this simple
and avoid writing a whole "mini-application" to do this.
Copying and
pasting the contents of classic.cfm into my <cfmail>
tag works so well, but
I just want to find the extra debug output that you get at
the top of your
error screen on an MX server like this:
http://brad.melendy.com/cf-error-full.jpg
I'm still hopeful that someone out there knows where the the
code that
builds this portion of the debug output exists. Thanks again.
...Brad
"dave.cozens" <[email protected]> wrote in
message
news:ei4vud$1uj$[email protected]..
What I've one previously when using CFERROR is to loop over
the available
structures: -
cferror,variables,request,session,application,server,client,url,form,cgi
and output the contents into an HTML string (using
CFSavecontent).
From there I can either email it of (very messy with
multiple member
support
teams) or (this is my preferred option) create an html file
(write it to the
server) and email out a reference to the file.
i.e.
1. Error occurs
2. Build detailed html page (use javascript "tabs" and
cfdump).
3. Write file with unique reference using time, date, server
etc.
4. Email support email with cferror detail and the unique
reference as a
hyperlink.
If you take it further you can categorise errors, write them
to a database
and
produce statistics. Which is very useful if you've got some
legacy code and
you
need to prioritise your errors.