>
> What is going on???
>
> I have this in a circuit in my application.
>
>
> What happens is my CircuitB is called corrected, except that instead of
> doing FuseactionX, as specified by the attribute, it tries to do
> AFuseaction, specified in the surrounding CFCASE.
>
OK...
Got it!!!
What's happening is that form/url variables that are available to the
CircuitA become available to CircuitB when I cfinclude/cfmodule to it.
cf_formurl2attributes then picks these up and replaces those that I've
passed through from CircuitA. This means that fuseaction that is passed to
CircuitA via a form overwrites the fuseaction passed in the CFMODULE as soon
as the cf_formurl2attributes is hit!
[shakes head embarrased] I always wondered what the point of the <cfif not
IsDefined("attributes.fusebox")> around <Cf_formurl2attributes> was! Now I
do! D'oh!
Regards
Stephen
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
