First of all I would like to thank everyone for answering my question about
encompassing blocks of code with the <cfoutput> tag. All the advice have
given me some direction.
I am really new to fusebox for that matter Coldfusion in general. I am
going through a RAMBO style of learning. Please bare with me with the type
of questions I ask. I inherited a non-fusebox application and I am
attempting to replace the infrastructure to a more manageable FUSEBOX
structure.
My current application have a MAIN fusebox with several sub-circuit
applications each with its own fusebox. By the way, I have briefly read the
electronic version of the fusebox methodology and looked over the code for
fusebox.org.
-- HR - Main Fusebox (app_globals, app_locals, app_server, index)
* Login - Circuit fusebox (app_locals, index)
* User - Circuit fusebox (app_locals, index)
* Project - Circuit fusebox (app_locals, index)
I am definitely missing the fundamental understanding of the persistencies
of session and request variables. For instance:
* I would setup <cfapplication> tag to allow me to have session
variables in the app_global template with a timeout of
�sessiontimeout="#CreateTimeSpan(0,23,0,0)#"�. I would then use the session
variable to store my login user id which is located on a sub-directory. I
have found that I am experiencing that the session variable is not defined
when I reference the variable in the Project directory. I have also
included the app_globals to all the circuit fuseboxes.
* Also, I have experienced that at times I would have a
non-reconizable attribute.fuseaction variable when calling a index template.
* Another strange problem that I am spending a lot of time on is the
following example. On the same template I would have the following:
<form action=�index.cfm?&#request.urltoken#� method=�post�>
<input type=�hidden� name=�fuseaction� value=�
displayProjectDetails�>
<input type=�submit� name=�submit� value=�
ProjectDetails�>
</form>
<a href=�index.cfm?fuseaction=�displayProjectDetails�
&#request.urltoken#>ProjectDetails</a>
* The submit button works but the link doesn�t. Sure it gets to the
proper template but the session variables are suddenly not defined. I don�t
understand why the persistencie of the session variable is suddenly lost in
space.
* I am also using request variables. Actually, I am under the
assumption that request variables stores values on the local workstation and
not on the server as it is with session or client variables. I am
attempting to use only request variables vs session variables.
Nevertheless, I am still have strange persistency issues.
Basically, all in all, I really do not know how what destroys the
persistency of the session and/or request variables.
Kinley Pon
Westcar Consulting Group, Inc.
mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
