<[EMAIL PROTECTED]> wrote:
> Personally I am never using CFSETTING ENABLECFOUTPUTONLY, instead I am
> 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!
>
I am not using cfsetting in the CFC -- I am using it in the calling
code. In my CFC I have output="false" for the cfcomponent and all my
cffunction tags. So I'm not breaking encapsulation, rather the CF
engine is by applying the cfsetting in my calling code to my CFC as
well. Perhaps this is a bug? That's not a rhetorical question -- I'm
honestly not sure.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
