Being that it's a required field, it's interesting that the CF-induced
client side error checking isn't picking it up either.

A few thoughts:

(1) Dump the form scope into your error emails.  It may give you some
insight.
(2) Are you doing any server-side form error checking?  Could that be
causing an issue?
(3) Is it possible that the form is getting submitted by a bot (and
therefore, bypassing the CF/JavaScript error checking)?  If possible,
you might want to throw some CAPTCHA on the form and see if it makes a
difference.

-S.

-----Original Message-----
From: Steve Moore [mailto:[email protected]] 
Sent: Tuesday, November 10, 2009 1:05 PM
To: cf-talk
Subject: Missing Form Fields


I have some CF forms that use dynamic field naming in a loop depending
upon some value. Code like:

<cfloop index="i" from="1" to="#form.number#">
<cfinput type="text" name="fname_#i#" size="20" maxlength="50"
required="yes">
<cfinput type="text" name="lname_#i#" size="20" maxlength="50"
required="yes">
</cfloop>

Every once in awhile when the user submits the form, one of the fields
does not exist on the page processing the form. The error is something
like "Element fname_2 is undefined in a Java object of type class
coldfusion.filter.FormScope." I've never experienced this myself to be
able to look at the source code of the form page, just emails generated
from the error. Thus I cannot determine if it's ColdFusion not
generating the field or the browser not sending it. This has happened in
different browsers, mostly IE (even version 8).

Has anyone experienced these types of issues? I've had it on CF 8, CF 9.




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Want to reach the ColdFusion community with something they want? Let them know 
on the House of Fusion mailing lists
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:328210
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to