It's not an issue with CFSAVECONTENT, it's an issue with custom tags. CFSAVECONTENT happens to be implemented as a custom tag (i.e. written in CFML), so it's subject to the same rules as other custom tags. If CFSAVECONTENT were to be implemented natively and designed to work as you propose, then the problem could probably be avoided, but the issue would still persist with custom tags as a whole.
cheers, barneyb On Wed, 23 Feb 2005 13:57:38 -0000, Adam Cameron <[EMAIL PROTECTED]> wrote: > >Re: CFFLUSH - I can't think of any reason that CFFLUSH would introduce a > bug when used in CFSAVECONTENT. Especially since this code works just fine: > > Nor I. I don't see what one has got to do with the other, to be honest. > > <cfflush>: flush the buffer. > <cfsavecontent />: don't put this stuff in the buffer. > > Why would they clash? > -- > > Adam > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
