Use CFSILENT

February 7, 2006 by Pete Freitag

Here's my tip for the day. If you have a choice in using either the cfsilent tag, or cfsetting enablecfoutputonly="true" use cfsilent.

Here's why

Easier to type
Easier to read
The enablecfoutputonly gets very messy when used across cfinclude calls.

There are probably some cases where using enablecfoutputonly makes sense, but in most cases I think you will find that cfsilent works well, and yields much cleaner code.

The Fixinator Code Security Scanner for ColdFusion & CFML is an easy to use security tool that every CF developer can use. It can also easily integrate into CI for automatic scanning on every commit.

Comments

Eric February 7, 2006

I've never had trouble using enableCFoutputOnly. I put it in one cfSetting tag in Application.cfm and enclose everything that has to render in cfOutput tags.

Pete Freitag February 7, 2006

Eric a problem could arise if you want to use some third party code that assumed enablecfoutputonly was not on.

Christopher Wigginton February 7, 2006

Ya should try trim filter. http://weblogs.macromedia.com/cantrell/archives/2005/01/eliminate_coldf.cfm

Related Posts

Comments