Alan,
You are almost there. Define the default values of request.headerfile and
request.footerfile in app_globals. Should you need a different
header/footer for a certain fuseaction or curcuit, you can always set a new
value in the corresponding index.cfm or app_locals.
Regarding your second question, cf_bodycontent is wrapped only around your
cfswitch; the call to app_layout comes next, e.g.:
<cf_bodycontent>
<cfswitch expression="#Attributes.Fuseaction#"
<cfcase....>
<cfcase....>
<cfcase....>
<cfcase....>
</cfswitch>
</cf_bodycontent>
<cfinclude template="app_locals.cfm">
-----Original Message-----
From: Alan Walker [mailto:[EMAIL PROTECTED]]
Sent: Donnerstag, 18. Januar 2001 20:19
To: Fusebox
Subject: Confusion wrapped around app_layout.cfm
Hello Everyone,
I'm starting to use CF_BODYCONTENT on a site I'm developing and I'm trying
to make sense of the app_layout.cfm file. I looked at the example code from
fusebox.org (below)
<cfparam name="request.headerfile">
<cfparam name="request.footerfile">
<cfparam name="request.bodycontent">
<cfparam name="attributes.showbody" default="yes">
<cfif len(request.headerfile)>
<cfinclude template="#request.headerfile#">
</cfif>
<cfif attributes.showbody>
<cfoutput>#request.bodycontent#</cfoutput>
</cfif>
<cfif len(request.footerfile)>
<cfinclude template="#request.footerfile#">
</cfif>
My question is, where do you actually create the file reference for the
#request.headerfile# and #request.footerfile#? Is this the right place to
assign that variable? Then on the actual index page, all you have is the
CF_BODYCONTENT tag wrapped around the CFSWITCH tag and then the
app_layout.cfm include. Is that right?
Thanks for your help,
Alan Walker
PlanetAlan.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
