Adobe Dreamweaver Forums



Last 10 THreads :         Dumb CSS question re: graphic alignment (Last Post : meinmichigan - Replies : 0 - Views : 1 )           »          Burn to a CD (Last Post : vodesjardins - Replies : 3 - Views : 4 )           »          Format numbers with leading zeros (Last Post : NedWebs - Replies : 1 - Views : 2 )           »          Event listener (Last Post : NedWebs - Replies : 3 - Views : 4 )           »          mouseover slide menu! ... help! (Last Post : openspark - Replies : 1 - Views : 2 )           »          Trouble with SQL Query Tool on Leopard (Last Post : Daverms - Replies : 8 - Views : 9 )           »          Re: Cannot paste text from MS Publisher into Dreamweaver (Last Post : Tim G - Replies : 8 - Views : 9 )           »          action script for button (Last Post : NedWebs - Replies : 5 - Views : 10 )           »          403 error from my domain? (Last Post : Ken Ford - *ACE* - Replies : 1 - Views : 4 )           »          Adding database RDS Login Dreamweaver 8 Coldfusion 8 (Last Post : ClubbyJMC2008 - Replies : 4 - Views : 5 )           »         


Home Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
User Info Statistics
Go Back   Adobe Dreamweaver Forums > Other Macromedia/Adobe Products > Cold Fusion
 
Tags:



Reply
  #1 (permalink)  
Old 10-08-2008, 11:22 PM
Rick Waugh
 
Posts: n/a
Diggs:
Default ColdFusion Error Handling Issue

We are currently upgrading from CF5 to CF8, finally. We have a site wide error
handling form, that captures the error information, and saves it into a
database, for an issue log application. The problem we are seeing in CF8 is
that the template information is missing. We get the original template, but if
the error is in an included template, then we don't see that info - we get the
line number, but only the base calling template name is shown. As we can have
quite a few includes, this is problematic.

We are using error.diagnostics, error.template, error.querystring. This used
to be sufficient, but is now apparently not. Is there anyway to get this
information out of another error variable, or step up the level or reporting on
the current process? It's painful tracing problems to their source.




Reply With Quote
Sponsored Links
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



© Camley Interactive (camley.info) 2008 - all logos and images are copywrite their respective owners.
Proud member of the Camley Interactive Network
All times are GMT. The time now is 01:42 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.1.0 ©2007, Crawlability, Inc.
Inactive Reminders By Mished.co.uk