ColdFusion can only route runtime errors to an error handler (your soft
error). Compile errors (such as invalid tag names) can't be interpreted
by ColdFusion and cause a hard error. Not much you can do about that.
-Carl V.
On 12/6/2012 8:39 AM, Robert Harrison wrote:
I have an exception
Search the HOF archives. I remember there is a thread about this topic. In
brief, error handlers only capture runtime exceptions. That is a compile error,
which happens before the code ever executes. So standard cfm error handlers
cannot capture it.
-Leigh
-talk
Subject: Re: CFERROR Handler
Search the HOF archives. I remember there is a thread about this topic. In
brief, error handlers only capture runtime exceptions. That is a compile error,
which happens before the code ever executes. So standard cfm error handlers
cannot capture it.
-Leigh
?
Steve
-Original Message-
From: Leigh [mailto:cfsearch...@yahoo.com]
Sent: Thursday, December 06, 2012 11:55 AM
To: cf-talk
Subject: Re: CFERROR Handler
Search the HOF archives. I remember there is a thread about this topic. In
brief, error handlers only capture runtime exceptions
IIRC I think site wide error handlers can catch it. However, compile errors in
prod applications is not the norm, since it would mean the code was never
tested.
-Leigh
--- On Thu, 12/6/12, DURETTE, STEVEN J sd1...@att.com wrote:
From: DURETTE, STEVEN J sd1...@att.com
Subject: RE: CFERROR
Seems to me if it generates an error which looks like a ColdFusion error then
we should be able to display something
other than that error. That is just a common security practice to NOT have
debug information go out to the public.
You can! This is why every application should include
Thank you all for the input. This was a simulation of the actual problem I'm
trying to address and your help gave me what I needed. What I'm really trying
to get fixed is server error that comes up in some situations; one of which is
the sample hard-error page I posted. I just needed to give
...@figleaf.com]
Sent: Thursday, December 06, 2012 1:19 PM
To: cf-talk
Subject: Re: CFERROR Handler
Seems to me if it generates an error which looks like a ColdFusion error then
we should be able to display something
other than that error. That is just a common security practice to NOT have
debug
trying setting the type to any and then it will show you the error and you
will be able to see what the error type is, maybe a different error is
occurring and it is not an exception type.
On Mon, Apr 4, 2011 at 10:35 AM, Jay Pandya jaypandy...@gmail.com wrote:
In my local when i am using
trying setting the type to any and then it will show you the error and you
will be able to see what the error type is, maybe a different error is
occurring and it is not an exception type.
I all ready tried those things.If i put the type as exception and exception as
any though,i am not getting
trying setting the type to any and then it will show you the error and you
will be able to see what the error type is, maybe a different error is
occurring and it is not an exception type.
All ready tried with exception as any.But when i am using type as exception it
is showing normal error
are you sure the error template you are pointing to exists at the path
specified in the CFERROR tag, and does not contain any errors itself ?
what happens if you browse directly to the error template ?
On Mon, Apr 4, 2011 at 7:06 PM, Jay Pandya jaypandy...@gmail.com wrote:
trying setting the
What CF version were you on before this recent upgrade to CF9? Try changing
the TYPE attribute in the CFError tag to type=exception, and see what
happens.
On Thu, Jan 28, 2010 at 2:41 PM, Tim Do t...@wng.com wrote:
We just upgraded to cf9 and my error handling is no longer working the way
not sent in a few
days. any other ideas?? I tried wrapping the error info into cfsavecontent
and still shows the error info and doesn't send.
-Original Message-
From: Qing Xia [mailto:txiasum...@gmail.com]
Sent: Thursday, January 28, 2010 11:53 AM
To: cf-talk
Subject: Re: cferror
the error info and doesn't send.
-Original Message-
From: Qing Xia [mailto:txiasum...@gmail.com]
Sent: Thursday, January 28, 2010 11:53 AM
To: cf-talk
Subject: Re: cferror / cfmail issue
What CF version were you on before this recent upgrade to CF9? Try changing
the TYPE attribute
]
Sent: Thursday, January 28, 2010 12:21 PM
To: cf-talk
Subject: Re: cferror / cfmail issue
When type=request, the error template is not supposed to contain any CFML
tags, and you may only refer to a handful of special variables in the error
scope.
When you said you have both and request
]
Sent: Thursday, January 28, 2010 12:21 PM
To: cf-talk
Subject: Re: cferror / cfmail issue
When type=request, the error template is not supposed to contain any CFML
tags, and you may only refer to a handful of special variables in the error
scope.
When you said you have both and request
]
Sent: Thursday, January 28, 2010 12:21 PM
To: cf-talk
Subject: Re: cferror / cfmail issue
When type=request, the error template is not supposed to contain any CFML
tags, and you may only refer to a handful of special variables in the error
scope.
When you said you have both and request
around it, I get nothing but the text from the errorPage.
-Original Message-
From: Qing Xia [mailto:txiasum...@gmail.com]
Sent: Thursday, January 28, 2010 12:21 PM
To: cf-talk
Subject: Re: cferror / cfmail issue
When type=request, the error template is not supposed to contain any CFML
Since you say that the E-mail does not get sent I would assume you
have an error in your error handler. Try simplifying the error E-mail
to send hello world to see if that works. If that works, build up
the code incrementally until it breaks.
Check all your log files to get hints on what the
Subject: Re: cferror / cfmail issue
Since you say that the E-mail does not get sent I would assume you
have an error in your error handler. Try simplifying the error E-mail
to send hello world to see if that works. If that works, build up
the code incrementally until it breaks.
Check all your log files
You can't remove the frames without a page referesh, but you should be
able to pull them all to zero width/height with JS to give the
appearance of a full page. However, I'd generally recommend
redirecting to a dedicated error page rather than showing errors
inline. If you do that, just
I'm trying to generate a custom error page of type request and still obtain
the
form.fieldnames. Is it possible to get the information from the parent page
once the
error page has been called?
No, the Form scope is unavailable in an error page when you use
TYPE=REQUEST. I would recommend
IIRC HTTPReferer is a CGI variable as in CGI.HTTPReferer check the docs on
what vars error returns.
G!
On Wed, Jan 7, 2009 at 2:49 PM, John P phasereve...@gmail.com wrote:
I'm setting up a cferror template that collects the following info.
INSERT INTO Errors(HTTPReferrer, Diags, Query,
Thanks G.
IIRC HTTPReferer is a CGI variable as in CGI.HTTPReferer check the docs on
what vars error returns.
G!
~|
Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to
date
Get the Free Trial
I'm not sure what version of CF you're running, however if its 7+ then I
would look at moving over to Application.cfc, its far more comprehensive in
a great many ways.
You can then use the onError() method to handle any exceptions thrown, it's
quite a bit cleaner.
Rob
-Original Message-
On testing it however (by using a .cfm file name that does not exists), I
still see the usual debug page with Error Occurred While Processing
Request message and not the error.cfm.
You'd need a missing template handler for that type of error. An error request
template won't catch it.
You'll
cferror is for errors that occur within cfm files. To catch a 404 you
are going to need to use your web server's error handling or use CF's
Missing Template Handler.
On 11/22/06, Michael E. Carluen [EMAIL PROTECTED] wrote:
Hi everyone.
I am currently adding a basic custom error page on my
Michael,
A template error is thrown before anything else. You'll need to
handle those through your missing template handler - which you can
set in the CFAdmin.
Jon
On Nov 22, 2006, at 3:58 PM, Michael E. Carluen wrote:
On testing it however (by using a .cfm file name that does not
Oops didn't mean to dog pile on that response :-)
I see Will and Ray already got it covered...
On Nov 22, 2006, at 4:33 PM, Jon Clausen wrote:
Michael,
A template error is thrown before anything else. You'll need to
handle those through your missing template handler - which you can
set in
Thanks Ray, Will, Jon,
For this app, I am currently using HMS on a shared server. This means I do
not have access to the CF Administrator for setting the .cfm missing
template handler. And HMS's (control panel) custom error template mgt only
catches .htm missing templates.
Can the missing
Unfortunately no. At least not as far as I know.
On 11/22/06, Michael E. Carluen [EMAIL PROTECTED] wrote:
Thanks Ray, Will, Jon,
For this app, I am currently using HMS on a shared server. This means I do
not have access to the CF Administrator for setting the .cfm missing
template handler.
[EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Wednesday, November 22, 2006 2:32 PM
Subject: Re: cferror on application.cfm not working (?)
Unfortunately no. At least not as far as I know.
On 11/22/06, Michael E. Carluen [EMAIL PROTECTED] wrote:
Thanks Ray, Will, Jon
Thanks for confirming Ray.
Anyway, I contacted HMS, and they were able to modify the server's IIS 404
settings to include .cfm templates.
-Original Message-
From: Raymond Camden [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 22, 2006 2:33 PM
To: CF-Talk
Subject: Re: cferror
:[EMAIL PROTECTED]
Sent: 22 November 2006 22:15
To: CF-Talk
Subject: RE: cferror on application.cfm not working (?)
Thanks Ray, Will, Jon,
For this app, I am currently using HMS on a shared server. This means I do
not have access to the CF Administrator for setting the .cfm missing
template handler
Thanks very much for clearing this up Matt and Dave, I was using
type=request.
-Original Message-
From: Dave Watts
Sent: Wednesday, May 10, 2006 6:21 PM
To: CF-Talk
Subject: RE: Cferror and the site wide handler
snip
If I recall correctly, this is the execution order for error handlers
I am a bit confused as to the difference? When I use CFERror, I am using it
as a site-wide handler?
Then, I can use CFTRY/CFCATCH on individual pages.
Are you talking about 404 handlers??
...
Ben Nadel
Web Developer
Nylon Technology
350 7th Avenue
Floor 10
New York, NY
]
Sent: Wednesday, May 10, 2006 2:35 PM
To: CF-Talk
Subject: RE: Cferror and the site wide handler
I am a bit confused as to the difference? When I use CFERror, I am using
it as a site-wide handler?
Then, I can use CFTRY/CFCATCH on individual pages.
Are you talking about 404 handlers
.
-Original Message-
From: Steve Brownlee [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 10, 2006 2:42 PM
To: CF-Talk
Subject: RE: Cferror and the site wide handler
No, the site wide error handler is specified in the CF Admin under the
Server Settings Settings section. That will catch any
, 2006 2:42 PM
To: CF-Talk
Subject: RE: Cferror and the site wide handler
No, the site wide error handler is specified in the CF Admin under the
Server Settings Settings section. That will catch any error produced by
your site, and the processing will never make it to a page with CFERROR
It's only advantage, IMHO, is ease of deployment. It's certainly not
useful for detailed error reporting like Matt needs.
-Original Message-
From: Ben Nadel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 10, 2006 2:50 PM
To: CF-Talk
Subject: RE: Cferror and the site wide handler
Ahhh
Message-
From: Plunkett, Matthew [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 10, 2006 2:45 PM
To: CF-Talk
Subject: RE: Cferror and the site wide handler
Yes, I know where it is set. Thanks for confirming the order that they
are processed.
Now we have to find a new way to be secure (by hiding
Thanks, I will look at this details.cfm.
-Original Message-
From: Steve Brownlee
Sent: Wednesday, May 10, 2006 3:01 PM
To: CF-Talk
Subject: RE: Cferror and the site wide handler
Matt, I was responding to Ben there. Didn't intend to oversimplify for you
since you obviously knew about
Robertson
Sent: Wednesday, May 10, 2006 4:23 PM
To: CF-Talk
Subject: Re: Cferror and the site wide handler
Best way to look at error handling:
1. try/catch blocks are for situations where you have an expected potential
error (i.e. a mime type failure on a file upload) and you want to handle
this known
: 10 May 2006 19:45
To: CF-Talk
Subject: RE: Cferror and the site wide handler
Yes, I know where it is set. Thanks for confirming the order that they are
processed.
Now we have to find a new way to be secure (by hiding all the junk that
default errors reveal), but let the developers see what
Is it possible to use both cferror and the site wide handler
in MX 6.1?
My tests indicate that it is not possible, which is
unfortunate. It seems that the site wide will always take
precedence. Is there a way around that?
My guess is no, but thought I'd check anyway.
I care because
On 5/10/06, Plunkett, Matthew wrote:
My problem is that I have both 2 and 3 implemented. It seems that 2 never
hits unless I turn off 3. Is that expected, or is there a way around it?
That ain't right. Are you sure you are using type=EXCEPTION in the cferror
statement? Dave Watts put up an
Most likely you have an error in CustomError.cfm. If CF can't call the error
template page it gives the error of the original page.
Cheers,
Sam
On 10/14/05, Chad McCue [EMAIL PROTECTED] wrote:
I am running CF7on windows 2003.
I am trying to use CFERROR in my application.cfm file and it
It may have been a crazy dream but I thought I read
somewhere that when CF
enters an error state the performance of the server, or
more importantly
it's ability to serve pages, is impeded. Does anyone have
any thoughts or
links to any evidence to that effect? Specifically, we
have some
Minor revisions to the script:
cfset starttime = getTickCount()
cfloop index=x from=1 to=4000
cftrycfset y = x
cfcatch/cfcatch/cftry/cfloop
cfset ms = getTickCount()-starttime
cfset normal = ms
cfoutput
div
normal time = #ms# milliseconds
/div
/cfoutput
cfset
Thanks for the suggestion. On one of our boxes (without robust error
handling) processing times increase to 8 times with your script. I modified
it so it was still performing a division operation (y=x/1) to improve the
validity of the script.
I appreciate the ideas.
Adam
On 7/19/05, S.
I got:
normal time = 0 milliseconds
error time = 125 milliseconds
division by zero error!
-Original Message-
From: S.Isaac Dealey [mailto:[EMAIL PROTECTED]
Sent: 19 July 2005 15:49
To: CF-Talk
Subject: Re: CFError performance
Minor revisions to the script:
cfset starttime
Thanks for the suggestion. On one of our boxes (without
robust error
handling) processing times increase to 8 times with your
script. I modified
it so it was still performing a division operation (y=x/1)
to improve the
validity of the script.
Actually that makes the script invalid... As
I got:
normal time = 0 milliseconds
error time = 125 milliseconds
division by zero error!
Increase the number of iterations of the loop until normal time is at
least 1ms -- 400 is what worked on our server, but it's liable to
vary.
s. isaac dealey 954.522.6080
new epoch : isn't it time
No, I changed the y = x to y = x/1, of course the x/0 is still the error
condition. But thanks ;-)
On 7/19/05, S. Isaac Dealey [EMAIL PROTECTED] wrote:
Thanks for the suggestion. On one of our boxes (without
robust error
handling) processing times increase to 8 times with your
script.
No, I changed the y = x to y = x/1, of course the x/0 is
still the error condition. But thanks ;-)
Oh my misunderstanding ... nevermind... :)
s. isaac dealey 954.522.6080
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
You can use the Missing Template Handler in CFMX Admin.
Chris
-- Original Message --
From: Will Tomlinson [EMAIL PROTECTED]
Reply-To: cf-talk@houseoffusion.com
Date: Wed, 30 Mar 2005 20:40:29 -0400
cferror DEFINITELY will not catch missing file errors. I
Darn. You can use cftry/catch, with a catch type of missinginclude, but this
requires cftry/catch on the page, and can't be implemented globally (it's
intended for fine-grain exception handling)
Chris Norloff
-- Original Message --
From: Will Tomlinson
cferror DEFINITELY will not catch missing file errors. I just
had that one happen on my site, still trying to figure out a
way around it. :)
Did you set the missing template handler within the CF Administrator?
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software
Did you set the missing template handler within the CF Administrator?
I'm using Shared Hosting - No access.
Thanks,
Will
~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble
Ticket application
30, 2005 9:36 PM
To: CF-Talk cf-talk@houseoffusion.com
Subject: Re: cferror question
Did you set the missing template handler within the CF Administrator?
I'm using Shared Hosting - No access.
Thanks,
Will
~|
Logware
I tried cfoutput/cfoutput and cferror caught it without fail.
Perhaps something wrong in your error template causing it to fail?
Ken
On Mon, 24 Jan 2005 16:43:42 -0400, Robert Everland III
[EMAIL PROTECTED] wrote:
Why does cferror exception not catch an error like this cfoutput/cfoutput
, it
On Mon, 24 Jan 2005 16:43:42 -0400, Robert Everland III
[EMAIL PROTECTED] wrote:
Why does cferror exception not catch an error like this cfoutput/cfoutput
, it will just throw the error without being caught by cferror.
Because the CF engine doesn't even get as far as compiling the page.
If
Looks okay to me. The next thing I'd do is put cfdump var=#cferror# in the
exception handling template to see the cferror scope variables - maybe
something's not exactly as you expect (and you might check the cfcatch scope,
too).
Chris Norloff
-- Original Message
Hi Chris
I can see that when you dump out cferror, the thrown exception is stated
in the structure, my problem lies in that I can't seem to get Cold
Fusion to go to the correct template... The two scenarios are below and
it goes against what my thinking was...
- SCENARIO ONE TEMPLATE
cferror
I use a single CFERROR template which then does a CFSWITCH on
#error.rootcause.type# to pick the actual type of the exception, and then
process accordingly (redirect, email, just error to screen, log, whatever).
The 'rootcause' in there goes inside the CFErrorWrapper to the original
exception.I
Have you tried examining the CFERROR struct that is returned for the error type and then conditionally cflocating the user to the login page, if it's a notLoggedIn error and running a CFRETHROW if it's not?
Jeff
- Original Message -
From: Marlon Moyer
To: CF-Talk
Sent: Thursday, June
PROTECTED]
Sent: Thursday, June 10, 2004 12:15 PM
To: CF-Talk
Subject: RE: CFError bummer
I use a single CFERROR template which then does a CFSWITCH on
#error.rootcause.type# to pick the actual type of the exception, and
then
process accordingly (redirect, email, just error to screen, log
This is 100% opinion, but CFERROR should be a last ditch effort to make sure
no error messages appear on the screen.You should always use one, but all
your actual error trapping should be done with CFTRY..CFCATCH if at all
possible.
If you're using something like Fusebox or Mach-ii, it's a snap,
I'm trying to implement some site-wide error handling using
cferror, and it's really being a PITA.
In my application.cfm file, at the very end, I have:
cferror type=EXCEPTION template=/error/error.cfm exception=ANY
cferror type=REQUEST template=/error/404.cfm
error.cfm and 404.cfm are
This is 100% opinion, but CFERROR should be a last ditch
effort to make sure no error messages appear on the screen.
You should always use one, but all your actual error trapping
should be done with CFTRY..CFCATCH if at all possible.
I would strongly disagree with this (not that my opinion
This is 100% opinion, but CFERROR should be a last ditch effort to make
sure
no error messages appear on the screen.You should always use one, but
all
your actual error trapping should be done with CFTRY..CFCATCH if at all
possible.
This goes against the whole idea of how exception handling
I have setup cferror my application.cfm, with a type of
REQUEST that calls a local CF page. For some reason, when
a syntax error occurs, the tag does not get called, and
the standard error code shows. Any Ideas? I have included
the code.
Well, first of all, there's no such variable as
Yes, it is.
Dave
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 14, 2003 4:45 PM
To: CF-Talk
Subject: RE: CFERROR
I have setup cferror my application.cfm, with a type of
REQUEST that calls a local CF page. For some reason, when
a syntax
Is your error page in the same directory as your
Application.cfm file?
Yes, it is.
You might try creating a new directory, copying your error page to it, and
creating a new Application.cfm with a CFERROR tag, and a page with an error,
within that directory, just to see if you can get it to
Type request is only called if no other handler catches the error. In your case, you
probably have an error page defined in the administrator.
-Oorspronkelijk bericht-
Van: Dave Sueltenfuss [mailto:[EMAIL PROTECTED]
Verzonden: vr 12/09/2003 15:48
Aan:
No, there is no error page defined in the CFAdmin.
Dave
-Original Message-
From: Pascal Peters [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 11:01 AM
To: CF-Talk
Subject: RE: CFERROR
Type request is only called if no other handler catches the error. In
your case, you
Use type=exception
- Original Message -
From: Dave Sueltenfuss [EMAIL PROTECTED]
Date: Friday, September 12, 2003 9:01 am
Subject: RE: CFERROR
No, there is no error page defined in the CFAdmin.
Dave
-Original Message-
From: Pascal Peters [EMAIL PROTECTED]
Sent
ie on the MAC sucks IMHO..
It addeds padded spaces and breaks when input ... type=file isn't the
last element
WG
-Original Message-
From: Scott Mulholland [mailto:[EMAIL PROTECTED]
Sent: 02 June 2003 15:34
To: CF-Talk
Subject: cferror oddities (revisited)
I posted a week or so ago,
I believe that when you submit a form on a mac it often sends at least
one white space even from an 'empty' field. fix: trim() all form input.
(a nuisance)
I have also had trouble in macs when you have a form with
ENCTYPE=MULTIPART/FORM-DATA which you need in forms with a input type
= file
-
From: Richard Meredith-Hardy [mailto:[EMAIL PROTECTED]
Sent: Monday, June 02, 2003 10:22 AM
To: CF-Talk
Subject: Re: cferror oddities (revisited)
I believe that when you submit a form on a mac it often sends at least
one white space even from an 'empty' field. fix: trim() all form input
The referer is the page before where the error happened, so whether or not
the variables exist on that page is irrelevant. That's just listed so you
can figure out what page the user made the request that caused the error
from.
The query string should never be empty if you've got a fusebox app,
.
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 27, 2003 3:54 PM
To: CF-Talk
Subject: RE: cferror oddness?
The referer is the page before where the error happened, so whether or
not the variables exist on that page is irrelevant. That's just listed
so you can
On Wednesday 12 Feb 2003 17:30 pm, Kevin Langevin wrote:
(and saved me from more concussions from beating my head against a wall)
My wall already has a big dent... I think I should buy some padding... ;-)
that ANY error in the error template causes CF to default back to the
default error
On Wednesday 12 Feb 2003 12:47 pm, Craig Dudley wrote:
The template specified in cferror CANNOT run cfml, any cfml at all,
not even a cfif.
This is not the case for TYPE=Exception on MX.
See the URL quoted.
--
Tom C
Listen to Ivanova's suggestions.
: Thomas Chiverton [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 12:17 PM
To: CF-Talk
Subject: Re: cferror
On Wednesday 12 Feb 2003 12:47 pm, Craig Dudley wrote:
The template specified in cferror CANNOT run cfml, any cfml at all,
not even a cfif.
This is not the case for TYPE
On Tuesday 11 Feb 2003 17:44 pm, Thomas Chiverton wrote:
On Tuesday 11 Feb 2003 15:32 pm, Mosh Teitelbaum wrote:
2. Debug your CFMAIL code/settings based on the gray-box CF error that is
currently being shown.
They gray-box error is just the one that caused the exception (I'm
deliberatly
The template specified in cferror CANNOT run cfml, any cfml at all,
not even a cfif.
That's your problem.
-Original Message-
From: Thomas Chiverton [mailto:[EMAIL PROTECTED]]
Sent: 12 February 2003 10:21
To: CF-Talk
Subject: Re: cferror
On Tuesday 11 Feb 2003 17:44 pm, Thomas
The cfmail tag should have the parameter server instead of
mailserver
Chip
-Original Message-
From: Thomas Chiverton [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 11, 2003 11:23 AM
To: CF-Talk
Subject: Re: cferror
On Tuesday 11 Feb 2003 15:28 pm, Scott Brady wrote:
Most likely
The template specified in cferror CANNOT run cfml, any cfml at all,
not even a cfif.
*Buzz!* Thank you for playing.
That is only true for Error Type REQUEST.
I use an error template that e-mails me every EXCEPTION. I use CFMAIL,
CFDUMP, CFLOOP and several other CFML tags on that template.
Is it possible that you have an exception on the handler page?
D.
Thomas Chiverton wrote:
I'm reading
http://livedocs.macromedia.com/cfmxdocs/Developing_ColdFusion_MX_Applications_with_CFML/Errors6.jsp#1126158
with regards to placing a site wide handler in Application.cfm.
To this end,
From: Thomas Chiverton [EMAIL PROTECTED]
To this end, I've got
cferror type=Exception
template=error.cfm
mailTo=[EMAIL PROTECTED]
after the cfapplication tag.
This all works fine, till I use cfmail in the error page, then I get just the
normal coldfusion gray error box on
On Tuesday 11 Feb 2003 15:28 pm, Scott Brady wrote:
Most likely, there's a problem in your cfmail code (or something else on
your error page, but I'm guessing that it's the cfmail code). Maybe post
your cfmail code and someone will spot the problem?
cfmail to=[EMAIL PROTECTED] subject=err
Tom:
There may well be an error in your CFMAIL code or settings. When an error
is generated inside of a CFERROR error handler, an error is thrown that
cannot be caught with TYPE=Exception. It can only be caught by
TYPE=Request which does not allow the use of CFML. So you should do two
things:
On Tuesday 11 Feb 2003 15:32 pm, Mosh Teitelbaum wrote:
2. Debug your CFMAIL code/settings based on the gray-box CF error that is
currently being shown.
They gray-box error is just the one that caused the exception (I'm deliberatly
breaking a database call) though.
I'll try your suggestion.
Tim:
The two should be mutually exclusive as the JS alert is client-side and
CFERROR only traps errors that occur within ColdFusion (i.e., server-side).
When you say that a JS alert is encountered, do you mean that the JS dialog
box pops-up or do you mean whenever you have the alert code in a
Rick... sorry I didn't respond sooner about your initial blank screen
.. I think that was the same problemquestion
-Original Message-
From: Rick Faircloth [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 2:04 AM
To: CF-Talk
Subject: RE: cferror
Thanks for the in-depth
No problem, Tim.
Sometimes it's hard to keep up with these mailing list conversations!
Thanks for your help!
Rick
-Original Message-
From: Tim Laureska [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 6:27 AM
To: CF-Talk
Subject: RE: cferror
Rick... sorry I didn't
Here's my notes on cferror types (CF 4.5 SP2, Solaris, Oracle 8i):
Chris Norloff
type=expression
- catches bad expression like select * from m_job_summary where
job_id=#doesnt_exist#
type=database
- catches bad SQL like select * from m_job_summary GROUP ORDER BY
-
with any additional information that would help
us fix this problem, please send E-Mail to: A
HREF=mailto:#ERROR.MailTo#;#ERROR.MailTo#/A.
Tim Laureska
-Original Message-
From: Chris Norloff [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 8:26 AM
To: CF-Talk
Subject: RE
1 - 100 of 182 matches
Mail list logo
