> It does that because the features (cfsetting and cfsavecontent) are
> encapsulated from each other... cfsavecontent in particular doesn't do
> anything other than examine what's put into the output buffer and
> capture it out into a variable. So when you have cfsetting set to
> disable content to the buffer outside of cfoutput, no data reaches the
> buffer and therefore cfsavecontent doesn't "see" anything to capture.
> It is the same as if you were to put this in a custom tag:
>
> <cfif thistag.executionmode is "end">
> <cfset "caller.#attributes.variable#" = thistag.generatedcontent>
> <cfset thistag.generatedcontent = "">
> </cfif>
>
> If nothing reaches the server's output buffer, then the
> thistag.generatedcontent variable would be empty, and cfsavecontent is
> the same way.
>
Yeah, that's right in line with what Dave Watts said. I didn't realize
that these tags were implemented as custom tags (relative to other
tags like cfhttp). Knowing that makes all the difference.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
