Contents > CFML Reference > ColdFusion Tags > cfsetting

cfsetting

Controls aspects of page processing, such as the output of HTML code in pages.

Page processing tags, Variable manipulation tags

<cfsetting 
   enableCFoutputOnly = "Yes" or "No" 
   showDebugOutput = "Yes" or "No" 
   requestTimeOut = "value in seconds" >

cfcache, cfflush, cfheader, cfhtmlhead, cfinclude, cfsilent

ColdFusion MX 6.1: Changed behavior: if the tag has a body, ColdFusion executes its contents.

ColdFusion MX:

• Added the requestTimeOut attribute.
• The catchExceptionsByPattern attribute is obsolete. It does not work, and causes an error, in releases later than ColdFusion 5.
• Changed exception handling: the structured exception manager searches for the best-fit cfcatch handler. (In earlier releases, an exception was handled by the first cfcatch block that could handle an exception of its type.)

The cfsetting requestTimeout attribute replaces the use of requestTmeOut within a URL. To enforce a page timeout, detect the URL variable and use code such as the following to change the page timeout:

<cfsetting RequestTimeout = "#URL.RequestTimeout#"> 

You can use this tag to manage whitespace in ColdFusion output pages.

If you nest cfsetting tags: to make HTML output visible, you must match each enableCFoutputOnly = "Yes" statement with an enableCFoutputOnly = "No" statement. For example, after five enableCFoutputOnly = "Yes" statements, to enable HTML output, you must have five corresponding enableCFoutputOnly = "No" statements.

If HTML output is enabled (no matter how many enableCFoutputOnly = "No" statements have been processed) the first enableCFoutputOnly = "Yes" statement blocks output.

Note: If the debugging service is enabled and showDebugOutput =" Yes", the IsDebugMode function returns Yes; otherwise, No. ColdFusion MX 6.1 allows a </cfsetting> end tag; however, this end tag does not effect processing. The cfsetting attributes affect code inside and outside the cfsetting tag body. ColdFusion MX ignored code between cfsetting start and end tags.

<p>CFSETTING is used to control the output of HTML code in ColdFusion pages. 
   This tag can be used to minimize the amount of generated whitespace.

<cfsetting enableCFoutputOnly = "Yes">
   This text is not shown
<cfsetting enableCFoutputOnly = "No">
   <p>This text is shown
<cfsetting enableCFoutputOnly = "Yes">
   <cfoutput>
      <p>Text within cfoutput is always shown
   </cfoutput>   
<cfsetting enableCFoutputOnly = "No">
   <cfoutput>
      <p>Text within cfoutput is always shown
   </cfoutput>   

Contents > CFML Reference > ColdFusion Tags > cfsetting

ColdFusion 8 | ColdFusion MX 7 | ColdFusion MX 6.1 | ColdFusion MX | Forums | Developer Center | Bug Reporting

Version 6.1

Comments are no longer accepted for ColdFusion MX 6.1. ColdFusion 8 is the current version.

Comments

Add Comment

sporter said on Aug 14, 2003 at 7:04 AM :

What does "if the tag has a body, ColdFusion executes its contents" mean?

jrunrandy said on Aug 14, 2003 at 1:56 PM :

In CFMX 6.1, cfsetting can have an end tag: </cfsetting> and ColdFusion executes the code between <cfsetting> and </cfsetting>.

No screen name said on Feb 19, 2004 at 1:07 PM :

But what's the difference in executing code inside the <CFSETTING> compared to the code outside the <CFSETTING> ? Would there really be a reason to use a </CFSETTING> ? Or were some people using it, and this was a solution to make sure it just always works?

halL said on Feb 23, 2004 at 10:06 AM :

The initial Macromedia response may not be clear.
The end tag is allowed, but has no effect.
ColdFusion processes anything between the <cfsetting> and </cfsetting> in the same way
it processes code following the </cfsetting> tag.

No screen name said on Feb 11, 2005 at 10:59 AM :

The <cfsetting EnableCfOutputOnly="yes"> does not appear to work when used within custom tags. When I call my custom tag, all text in the tag body is output regardless of what I do with <cfsetting>

No screen name said on Nov 2, 2005 at 9:02 AM :

<typo> The cfsetting requestTimeout attribute replaces the use of

requestTimeOut <--- add an "i"

within a URL.

No screen name said on Nov 9, 2005 at 4:19 AM :

enableCFOutputOnly should say Optional not Required, as you then give an example where it's not specified:
<cfsetting RequestTimeout = "#URL.RequestTimeout#">

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/coldfusion/6.1/htmldocs/tags-pc6.htm

Add Comment