I believe these can be nested without worrying. I've never had a problem
embedding <cfsetting ENABLECFOUTPUTONLY> within custom tags, regardless of
how the templates calling those tags are constructed. Just set it ="yes" at
the top and ="no" at the bottom. Make _sure_ you set it ="no", however,
before exiting the tag - don't jump out of the middle of the tag without
doing so.
Jim
----- Original Message -----
From: "Ryan" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Monday, January 22, 2001 9:56 AM
Subject: Sometimes I get so sick of CF being weak.... please help
> In one of my custom tags I need to turn on ENABLECFOUTPUTONLY because
> the result of this custom tag will be going inside PRE tags, so I
> can't have any extra white space come out of it. Now the page that
> uses this tag quit working, becuase the ENABLECFOUTPUTONLY is affecting
> the entire request. Doesn't it make sense that it would only affect
> the custom tag? Shouldn't that be a separate 'scope'? It is with
> variables, why does the cfsetting carry across?
>
> So anyway, I need to turn ENABLECFOUTPUTONLY back off at the end of
> the custom tag, I guess. But what if (later on in development) a page
makes
> use of this tag, and that page already has ENABLECFOUTPUTONLY set to
> on? Then the tag will turn it on again, no problem there, but at the
> end of the tag it will set ENABLECFOUTPUTONLY to off, totally screwing
> up the page that calls it.
>
> Is there a way to detect ENABLECFOUTPUTONLY, so I don't need to flip
> it if I don't need to?
>
> I miss Perl...
>
> Thanks for any help.
>
> Ryan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
