So, I've just discovered something strange. When using a cferror tag that
calls an error template, it would appear that you are affectively
"cfincluding" that error template, as opposed to "cflocating" to that error
template. (Even though the includes within the error template itself
function as though the you were cflocating to that template.)
In other words, if you have a subdirectory Application.cfm that has an error
tag that calls a template in an above Application.cfm, any variables you
might have in the above level Application.cfm are not defined if the error
comes from below.
I had always understood it to be that you were effectively boucing out of
your existing application to the application within which the error template
resides. But, I was, apparently, wrong.
This is with CF 5.0, by the way. Not sure how it works with MX.
Thought I'd share in case this was biting anyone else in the butt.
-d
--
Deanna Schneider
UWEX-Cooperative Extension
Interactive Media Developer
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
