using cfsilent (for plain templates) and output="no" for cfc/cffunction.
Since the cfsetting/enabelcfoutputonly is set for the whole request,
until the cfsetting is changed, I feel that it breaks encapsulation --
one loses control/overview over where it is set and not when using a
chain of includes. If it is used then I would use it application-wide,
but for now I am happy with cfsilent!
--
Hugo Ahlenius
-------------------------------------------------------------
Hugo Ahlenius E-Mail: [EMAIL PROTECTED]
Project Officer Phone: +46 8 230460
UNEP GRID-Arendal Fax: +46 8 230441
Stockholm Office Mobile: +46 733 467111
WWW: http://www.grida.no
-------------------------------------------------------------
| -----Original Message-----
| From: Stephen Moretti (cfmaster) [mailto:[EMAIL PROTECTED]
| Sent: Tuesday, July 20, 2004 12:30
| To: CF-Talk
| Subject: Re: cfset vs. cfsavecontent
|
| Dave Carabetta wrote:
|
| > >
| > > When I wrapped a CFSETTING ENABLECFOUTPUTONLY around it, though, I
| > got the
| > > same error you did.
| >
| > Interesting. On a hunch after looking through your sample above, I
| > switched back to cfxml and simply put cfoutput after the
| opening cfxml
| > and before the closing cfxml tag, and then did a cfreturn
| > toString(xmlObject) and it worked fine.
| >
| > At this point, I guess I need to settle on what's more
| intuitive for
| > the developer who comes after me, but that's a different matter.
| >
| I haven't tested this, but have you tried using cfsilent
| instead of "cfsetting enablecfoutputonly"?
|
| It may allow cfxml to work correctly without need to wrap it
| in cfoutput.....
|
| Just a thought of something to try.
|
| Stephen
|
|
|
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
