yeah, or you can even add a little code to cf_nesting
and have the tag set that variable for you.
> -----Original Message-----
> From: Walsh, Christopher [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 05, 2001 8:01 AM
> To: Fusebox
> Subject: RE: App_layout.cfm
>
>
> I set a variable in appLocals that points to the root directory...
> ie: one level down, <cfset request.siteroot = "../">
> two levels down, <cfset request.siteroot = "../../">
> then I use that var in my code...not messy at all
>
> Chris
>
>
> -----Original Message-----
> From: Mark Stewart [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 05, 2001 9:28 AM
> To: Fusebox
> Subject: RE: App_layout.cfm
>
>
> I generally create a CF mapping to the circuit app in CF administrator.
> This way, I don't have to worry about ../../../ - I find it to be a
> little bit neater and more readable. Then, in my fuses, I'll cfinclude
> my app_layout.cfm like, <cfinclude
> template="/circuitapp/app_layout.cfm">
>
> Mark
>
> -----Original Message-----
> From: Stacy Young [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 05, 2001 12:50 AM
> To: Fusebox
> Subject: App_layout.cfm
>
>
> Why is it that for my circuit apps to work properly I have to set the
> app_layout include to "../app_layout.cfm" as opposed to "app_layout.cfm"
> like the home circuit? I want the header/footer files to come from the
> home
> circuit. :\
>
> thanks!
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Get the mailserver that powers this list at http://www.coolfusion.com
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
