> > I tell people this too.. but I have to make the
> > exception of cfoutput blocks.. b/c if you surround an
> > include with a cfoutput and have variables in #'s
> > inside, they don't output. Anyone have a
> > philosophical view on why this is so.. or is that
> > "just the way it is"
Actually, you can't close custom tags in <cfinclude>s either if they are
opened elsewhere. This is a bit annoying. So <cfinclude> is not very much
like copying and pasting the code in at all, except for variable handling.
It boils down to not being allowed closing tags (e.g. </cfoutput>,
</cf_customtag>) without matching opening tags inside a template. The
template is parsed as a unit for this kind of error before processing (?)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
