Fusebox question 1

[iao]

I am having a little trouble with understanding variable scoping when it comes to fusebox.

If a form variable (form.variable) is set to an attribute variable (attributes.variable) on the fuseaction page, will this variable persist throughout the fusebox application (meaning, will the attribute variable act similar to a session variable)?

I was under the impresssion that it was supposed to, yet I don't see it working for me. For example:

if I have a form variable on a display page, and send it via the fuseaction to an action page, I can set the name of the variable to #Attributes.variablename# instead of #Form.variablename#. That way, if I go through another fuseaction, #Attributes.variablename# should still exist, unlike #Form.variablename#. But, this is not the case. The only way I can get it to persist for more than one fuseaction is if I create it as a session variable (#Session.variablename#).

Does this make any sense. If it does, any ideas on where I am going wrong?

 

[tleish]

No, the ATTRIBUTES scope does not persist across pages unless the application specifically passes it from page to page either through a form or url.

That's not what the ATTRIBUTES scope in Fusebox is meant for.

http://www.fusebox.org/specifications/largescale/index.cfm?Fuseaction=Techniques1

- tleish