Use CFSILENT
February 07, 2006
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
enablecfoutputonlygets very messy when used acrosscfincludes.
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.
Tweet
add to del.icio.usRelated Entries
- 6 Tags for ColdFusion beginners - April 5, 2005
- Regular Expressions with ColdFusion - a Howto Guide - December 19, 2003
- Announcing CFML Weekly Email - October 19, 2012
- Client Variable Cookie CFGLOBALS Includes Session Ids - July 14, 2011
- Maximum Security CFML - cfObjective Slides - May 17, 2011
Trackbacks
Trackback Address: 538/A0AE3ADEBD5451E4C826C0180EED0D74
Comments
On 02/07/2006 at 2:47:36 PM EST Eric wrote:
1
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.
On 02/07/2006 at 2:55:13 PM EST Pete Freitag wrote:
2
Eric a problem could arise if you want to use some third party code that assumed enablecfoutputonly was not on.
On 02/07/2006 at 3:39:46 PM EST Christopher Wigginton wrote:
3
Ya should try trim filter.
http://weblogs.macromedia.com/cantrell/archives/2005/01/eliminate_coldf.cfm
Post a Comment
Recent Entries
- Firefox Aurora now Supports Content Security Policy 1.0
- Writing Secure CFML cfObjective 2013 Slides
- Upgrading to Java 7 on Linux
- J2EE Sessions in CF10 Uses Secure Cookies
- Learn about ColdFusion Security at cfObjective 2013
- Session Loss and Session Fixation in ColdFusion
- FuseGuard 2.3 Released
- CKEditor Spell Checker Plugin
