Steven Springer wrote:
I'm not sure if Google groups will strip out the attachment, but here goes.Variables are made up to protect the innocent, but the problems are real.
Based on what I'm seeing it looks like the problem stems from the fact that, in this instance at any rate, there is no rootcause key in the error struct. When I comment out the bit about rootcause everything works fine. Specifically the following three lines in error_message.cfm:
<!---Error Type: #error.rootcause.type#<br />
Error Message: #Error.Rootcause.Message#<br />
Error Detail: #error.rootcause.detail#--->
Now what I'm not sure of is if rootcause never exists in OpenBD, or if
it just doesn't exist in this case, so at a minimum you'll want to put a
StructKeyExists check around things before trying to output anything in
rootcause:
<cfif StructKeyExists(error, "rootcause")> ...I think since that itself was throwing errors (trying to output something that doesn't exist), i.e. you had errors in your error handler, it must not have been able to process further and just spit the code out to the page. That's my highly technical analysis anyway. ;-)
-- Matt Woodward [email protected] http://www.mattwoodward.com/blog Please do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments. http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
