cfinput

<cfinput 
   type = "input_type"
   name = "name"
   value = "initial_value"
   required = "Yes" or "No"
   range = "min_value, max_value"
   validate = "data_type"
   onValidate = "javascript_function"
   pattern = "regexp"
   message = "validation_msg"
   onError = "text"
   size = "integer"
   maxLength = "integer"
   checked 
   passThrough = "HTML_attributes">

passthrough="ID=""myID"""
passthrough='ID="myID"'

passThrough = "readonly = " "YES " " "

<!--- this example shows the use of cfinput within a cfform to ensure simple
validation of text items --->
<cfform action = "cfinput.cfm">
<!--- phone number validation --->
Phone Number Validation (enter a properly formatted phone number): <br>
<cfinput 
   type = "Text" name = "MyPhone" 
   message = "Enter telephone number,formatted xxx-xxx-xxxx (e.g. 617-761-2000)"
   validate = "telephone" required = "Yes">
   <font size = -1 color = red>Required</font>
<!--- zip code validation --->
<p>Zip Code Validation (enter a properly formatted zip code):<br>
<cfinput 
   type = "Text" name = "MyZip" 
   message = "Enter zip code, formatted xxxxx or xxxxx-xxxx" 
   validate = "zipcode" required = "Yes">
   <font size = -1 color = red>Required</font>
<!--- range validation --->
<p>Range Validation (enter an integer from 1 to 5): <br>
<cfinput 
   type = "Text" name = "MyRange" range = "1,5" 
   message = "You must enter an integer from 1 to 5" 
   validate = "integer" required = "No">
<!--- date validation --->
<p>Date Validation (enter a properly formatted date):<br>
<cfinput 
   type = "Text" name = "MyDate" 
   message = "Enter a correctly formatted date (dd/mm/yy)" 
   validate = "date" required = "No">
<input 
   type = "Submit" name = "" 
   value = "send my information">
</cfform>

Comments

No screen name said on Aug 25, 2004 at 4:19 AM :

The onValidate parameter of CFInput (type=TEXT) seems to be ignored by the CF server if any of the fields on the CFForm have required set to YES

lbdas357 said on Nov 11, 2004 at 12:13 PM :

If we use the <CFINPUT Time validation how can we determine AM or PM?

Adam Cameron said on Dec 27, 2004 at 7:14 PM :

It'd be quite nice if these docs had a summary of JavaScript's regex patterns, rather than just telling us <cfinput> uses them (which in itself is not very helpful).
To save anyone time having to seek a reference out, I use this one (it's Microsoft, so strictly speaking JScript not JavaScript, but I've never come across an incompatibility yet):
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/js56jsgrpregexpsyntax.asp

wooddog said on Jan 26, 2005 at 8:17 AM :

There is a problem with the validate integer when using the cfinput='text'. It excepts .5 as an integer or any whole number with a decimal in front of it.

No screen name said on Jun 3, 2005 at 7:04 AM :

HTML attribute disabled would be useful to be added in next versions

jrunrandy said on Jun 29, 2005 at 12:59 PM :

I believe that cfinput supports a disabled attribute in CFMX 7: http://livedocs.macromedia.com/coldfusion/7/htmldocs/00000279.htm

lizk said on Jul 13, 2005 at 4:26 AM :

i have this tag in the form
<CFINPUT TYPE="text" name="DirPHoneNo"
value="#form.DirPHoneNo#" label="Project Director Telephone number Input Box" mask="999-999-9999" validateAt="onBlur" validate="telephone" required="yes" message="enter valid phone number">
onBlur is ignored if i enter only part of the phone number (2 digits insted of 10). Can't submit form- no error message, no validation message- just wouldn't submit. I have js page included as well. tried removing js page reference- no luck. Also tried different masking.
Another problem: when using mask, if enter some digits but not all, remaining spaces are replaced by 0's instead of throwing error

y_not_25 said on Aug 9, 2005 at 2:14 AM :

HTML attributes class and id would be useful to be added in next versions.

I use id to assign a Label to a check- or radio-box like:
<input type="checkbox" name="lorem" id="lorem_1" value="1" /><label for="lorem_1">Lorem</label>
(more comfotable would of course be a label-attribute in the cfinput, which generates an id and label tag... ;-) )

Here's a workaround for the class attribute, but the class-attribute would be nicer:
<span class="yourStyle"><cfinput [...] /></span>
define the style in the css like this:
yourStyle input
{
/* ...*/
}

thx

Devline said on Oct 9, 2005 at 2:58 PM :

cfinput supports a disabled attribute in CFMX 7, but it ignores the argument "no"

hpottash said on Apr 4, 2006 at 7:46 AM :

The documentation for onValidate could probably use an example... so here is one. If you give it something other than exactly what it is exspecting you get very odd behaviour across your whole form.

<head>
<script>
function validateCheese(formObj,InputObj,InputObjVal){
return (inputObj.value == "cheese");
}
</script>
</head>
<body>
<cfinput
type = "Text" name = "cheese"
message = "you did not entere cheese"
onValidate = "validateCheese" >
</body>

Note that the javascript function name is passed to onvalidate, but that it is not called as a function (there are no tailing parens). also note that the function definition requires three paramiters (this is important) and that it always returns a booliean value. Even if you don't want to use any of the params passed to the function you need to take them.

Glizman said on Jun 12, 2006 at 6:43 AM :

In response to hpottash and onValidate, I appreciate the example code. I experimented with it and see what might be causing the "strange form behavior". Javascript is case-sensitive. The second input parameter is not matched exactly in case in the return statement. By capitalizing the "i" in "inputObj.value", I got the function results to be consistent with the input field's value "cheese" onSubmit. Which reminds me, I had to add a submit button! The Javascript failing could be the reason for the other form oddities.

HTH

No screen name said on Dec 11, 2006 at 12:37 PM :

Some additional hints on Validate (which would've helped me to not have to figure out myself):

If you include a Validate attribute, the Message attribute will determine what is displayed if the error condition is met.

The Validate attribute should only include the function name, without parentheses, so a tag might be cfinput type="Text" name="PasswordConfirm" required="No" size="10" onvalidate="passwordsMustMatch" message="Passwords must match."

The function should return true or false, true if there's not an error, false if there is.

halL said on Dec 11, 2006 at 1:16 PM :

In the previous comment on the Validate attribute, the second paragraph refers to the onValidate attribute, not the validate attribute.