I am implementing a very similar fusebox structure as fusebox.org. That is,
EVERY fusebox, whether it is the root or circuit application, contains the
following code:
<cfinclude template="app_globals.cfm">
<cfinclude template="app_locals.cfm">
<cf_bodycontent>
<cfparam name="attributes.fuseaction" default="">
<cfswitch expression="#attributes.fuseaction#">
<cfcase value="help">
<cfinclude template="dsp_help.cfm">
</cfcase>
<cfdefaultcase>
<cfinclude template="dsp_homepage.cfm">
</cfdefaultcase>
</cfswitch>
</cf_bodycontent>
<cfinclude template="app_layout.cfm">
I came across a situation where within one circuit application directory, I
needed to have a fuse that actually call another fusebox of another circuit
application directory. For instance, I have a USER fusebox and PROJECT
fusebox. From the PROJECT fusebox I needed a dsp_userForm.cfm which is in
the USER fusebox. If I were to call this from within the PROJECT fusebox, I
would either end up struggling with the variables and/or have a
<cf_bodycontent> nested in another <cf_bodycontent>.
How can I avoid replicating the templates into another fusebox (circuit
application)?
I hope I make sense�
Kinley
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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