RE: application.cfc onError

2007-08-27 Thread Chad Gray
Oh wow! this server is not up to date. No wonder I was getting strange results from staging to production. Thanks! -Original Message- From: Peterson, Chris [mailto:[EMAIL PROTECTED] Sent: Monday, August 27, 2007 9:23 AM To: CF-Talk Subject: RE: application.cfc onError I googled for

RE: application.cfc onError

2007-08-27 Thread Peterson, Chris
I googled for 'cflocation application.cfc onerror' and this was the first result (the fix for it) http://www.coldfusionjedi.com/index.cfm/2005/9/28/Two-Nice-Fixes-in-Cold Fusion-701 You can either update to CF 7.01 (why are you not up to date??) or you can put this into your onError method:

Re: application.cfc onError

2007-01-16 Thread Raymond Camden
One tip - maybe do a structkeyexists on your exception values like type and tagcontext within rootcause. I see you using it for rootcause itself, but not the others. (Although message should always exist afaik.) Worse comes to worse - just mail a dump of the exception object and see the keys there

Re: application.cfc onError

2007-01-16 Thread Will Tomlinson
> I have started using application.cfc and sending an email when an > error occurs by placing a CFMail tag in the onError function. > > I have one user that when she is doing an insert on a table and is > taken back to the display page I get this error emailed to me. I think this was a bug. I k

Re: application.cfc onError

2007-01-16 Thread Josh Nathanson
> Anyone know what this java.lang.NullPointerException is? There is nothing > in the CF logs to help me figure out > what this error is. I have found that this error often pops up when you try to use a date function such as DateDiff or DateFormat, and the value you are passing to the function

Re: Application.CFC onError function and the tag.

2006-09-07 Thread Raymond Camden
I've never used cferror for form checking. You wouldn't think it better to handle the form checking in the same file as the form? Thats just my opinion. Anyway - if you use onError, you can check the exception type. It should contain the information there if I had to guess. On 9/7/06, Ian Skinner