> 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?
Here's an idea, set a variable in the Request scope that you keep the
current state of EnableCFOutputOnly, and then only set it ON when you need
it on
You can also keep a "Was" state, do that CF_ templates know what to set it
back to
Philip Arnold
Director
Certified ColdFusion Developer
ASP Multimedia Limited
T: +44 (0)20 8680 1133
"Websites for the real world"
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
**********************************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
