Are you using CF_BodyContent in both of the index.cfm files - Parent and
child?
If so - to turn off the header and footer being included in the child do:
<CFModule template="child/index.cfm" HeaderFile="" FooterFile="">
That will over prevent the header and footer files being included in the
child index.cfm
(sounds like that might have been your problem to start with :)
Noam
----------
From: Russell Jones [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, 20 September 2000 18:10
To: [EMAIL PROTECTED]
Subject: Re: [Fusebox] Fusebox as tag - Display problems!!!!
Noam,
Actually, I am using CF_BodyContent and I'm not quite sure what you
mean by:
> You can also override the header and footer files (if you use the
> CF_BodyContent)
I know what you mean by the rest of it, thanks!
:)
-Russ
--
Russell Jones
Webmaster
ImproveNow.com
Phone: 207.236.0146
e-mail: [EMAIL PROTECTED]
> From: BOROVOY Noam <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Wed, 20 Sep 2000 17:15:00 +0200
> To: [EMAIL PROTECTED]
> Subject: RE: [Fusebox] Fusebox as tag - Display problems!!!!
>
> There's no magic to it...
> A display within a display can get tricky, but you can just add an
attribute
> to the child fusebox named DisplayMenu and default it to "Yes" in
> app_globals.
> When calling as CFMODULE add it with a value of "No".
> You can also override the header and footer files (if you use the
> CF_BodyContent)
>
> HTH,
> Noam
> ----------
> From: Russell Jones [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, 20 September 2000 16:50
> To: [EMAIL PROTECTED]
> Subject: [Fusebox] Fusebox as tag - Display problems!!!!
>
> Someone in allaire's forums recently mentioned a problem that I am
> running
> into now.
>
> ====
>
> Calling a Fusebox application as a tag (i.e. calling the index.cfm
> file
> through cfmodule/cfinclude) can have advantages and disadvantages.
>
> The main advantage is that you can encapsulate complex file
> management and
> processes through the very simple tag structure that is built into
> ColdFusion. So instead of trying to figure out what files are
needed
> to do
> some action, you simple need to know the path of the index.cfm
file
> (i.e.
> template="/directory/index.cfm") the fuseaction you want to call
> (i.e.
> fuseaction=somefuseaction) and any other variables that are needed
> for that
> specific fuseaction.
>
> The main disadvantage is when dealing displays. For example if you
> include a
> layout display file that contains a menu within your application,
> then call
> that application from some parent application that already
contains
> that
> menu layout you'll end up with two menus on the page. Which is
most
> likely
> not what you want.
>
> * http://forums.allaire.com/devconf/Index.cfm?Message_ID=572223
>
> ====
>
> Have any of you run into this, and how did you over come it?
>
> I'm sitting at my desk right now, sipping a frosty cola beverage
> waiting for
> someone to chime in. Please feel free to email me directly.
>
> Thanks a ton.
>
> -Russ
>
>
>
----------------------------------------------------------------------------
> --
> To Unsubscribe visit
>
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with
'unsubscribe' in
> the body.
>
----------------------------------------------------------------------------
--
> To Unsubscribe visit
>
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with
'unsubscribe' in the
> body.
>
----------------------------------------------------------------------------
--
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
