Well it does seem apparent that slapping a single CFOUTPUT around the
index.cfm CFSWITCH isn't going to work. Bummer, because it sure works with
CFTRY/CFCATCH.
I guess for me the issue is that I use a ton of CFINCLUDEs and don't use
very many CFMODULEs. I've got quite a few templates that are really "blocks"
and aren't meant to be used in a standalone fashion. Sometimes these guys
are integrated into an existing CFOUTPUT loop, and sometimes they aren't
SoOoOo, let me ask this question. Is there some sort of tag that does the
following?: <CFOUTPUT_if_not_already>
I mean, from a code reuse standpoint, this would be great. Each template
that is going to be used as a 'block' could be wrapped in a conditional
CFOUTPUT, so that way you didn't have to worry about it.
I mean, to me, if the CF parser comes across a CFOUTPUT within a CFOUTPUT,
it oughtta just skip over that nested CFOUTPUT, and keep on going, since its
already in a CFOUTPUT state.
Alan McCollough
Web Programmer
Allaire Certified ColdFusion Developer
Alaska Native Medical Center
> -----Original Message-----
> From: Matthew Walker [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, November 30, 2000 3:30 PM
> To: Fusebox
> Subject: RE: <cfoutput>#request.variable#<cfoutput>
>
> > <CFOUTPUT>
> > <CFSWITCH ....>
> > {all the CFCASE statements for fuseactions}
> > </CFSWITCH>
> > </CFOUTPUT>
>
> Well, curiously enough, <cfoutput> doesn't get transmitted into cfmodules,
> cf_tags, and cfincludes. So you can't just put <cfoutput/> in index.cfm
> and
> then forget it.
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
