Another question about bodycontent...
is the following correct, or should the bodycontent tags be in a different
location with this new way of passing the fuseaction?
Thank you,
Jason
<!--- determine if I am to delegate this fuseaction --->
<cf_bodycontent> <!--- capture the fusebox for display in app_layout --->
<cfif listlen(attributes.fuseaction, '.') GT 1>
<cfinclude template="#listfirst(attributes.fuseaction, '.')#/index.cfm">
<cfelse>
<!--- ooh... I get this one eh? I will process this fuseaction then... --->
<cfswitch expression="#attributes.fuseaction#">
<cfcase value="edihome">
<cfset request.xfa.login = "login">
<cfinclude template="dsp_edihome.cfm">
</cfcase>
<cfcase value="login">
this is the login
</cfcase>
<!--- *** default fuseaction for error catching *** --->
<cfdefaultcase>
<cfoutput>
I have received the fuseaction:
<b>#attributes.fuseaction#</b>, and I
don't know what to do with it.
</cfoutput>
</cfdefaultcase>
</cfswitch>
</cfif>
</cf_bodycontent>
<!--- display the captured fuesbox --->
<cfinclude template="app_layout.cfm">
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
