about a year ago in the Blackstone, you cannot pass the cfcatch structure
(for it is a structure) as a type = struct to a function, it has to be type
= any. I think it had other problems with its structure identity as well.
TK
http://www.tomkitta.com
-----Original Message-----
From: Matt Robertson [mailto:[EMAIL PROTECTED]
Sent: Sunday, May 23, 2004 10:04 AM
To: CF-Talk
Subject: RE: Using CFCATCH to display default error messages
Stan Winchester wrote:
>I need to know what template is throwing the error and what line number
If you want *just* the line number of the final error you can use
"<b>Error on Line #CFCATCH.TAGCONTEXT[1]["LINE"]#</b>", and
cgi.path_translated will give you the path/template that the error
occurred on.
As was mentioned in an earlier post, the most comprehensive thing to do
is just cfdump out the cfcatch scope (or cfdump out the variables scope,
which includes cfcatch and any queries you may have run; see below). In
CF6+ at least, this will give you a very nice trail of nested templates;
i.e. foo.cfm on Line 100 called bar.cfm, which called woo.cfm on line 20
and Line 19 threw an error. It doesn't say that explicitly, but you'll
be able to figure it out by looking at the contents of the struct.
And of course you can dump out other scopes for a very comprehensive
snapshot of whats what when the error occurred. A lot of data, so if you
have a 1k-recordcount query on the current page and you dumped the
variables scope that would be a mighty big email.
--------------------------------------------
Matt Robertson [EMAIL PROTECTED]
MSB Designs, Inc. http://mysecretbase.com
--------------------------------------------
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
