With ColdFusion Professional 4.01, if you have this:
<CFSETTING ENABLECFOUTPUTONLY="Yes">
<CFOUTPUT>
...some HTML here...
<CFINCLUDE TEMPLATE="include.cfm">
</CFOUTPUT>
<CFSETTING ENABLECFOUTPUTONLY="No">
and include.cfm is
<CFSET variables.x = 100>
...lots of lines of CFCode here...
#variables.x#
from the point of view of CFSETTING, CFOUTPUT is being carried over within
the included file (ie, if you view the source, CFSETTING isn't suppressing
the whitespace within the included file).
However, from CFOUTPUTs point of view, it *hasn't* been carried over because
#variables.x# isn't evaluated - without an additional CFOUTPUT around it,
you'll see "#variables.x#". This just doesn't seem consistent.
As you must have another CFOUTPUT block to output variables within the
included file , why doesn't the first CFSETTING tag say "OK, the effects of
the CFOUTPUT block around the included file isn't carried over into it, so
I'll stop treating code within the included file as being wrapped within
CFOUTPUT and suppress whitespace within it"?
--
Aidan Whitehall <[EMAIL PROTECTED]>
Macromedia ColdFusion Developer
Fairbanks Environmental +44 (0)1695 51775
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
