New ColdFusion Error: Form Entries Incomplete Or Invalid
Posted June 12, 2007 at 10:06 AM
I just got a ColdFusion error that I have never seen before:
Form entries incomplete or invalid. Please go back an correct the problem.
Here is the uber-useful ColdFusion error screen:
| | | | ||
| |  | | ||
| | | |
This is about the most useless ColdFusion error ever! How could I even go about debugging this? They don't even give me a template or a line number or even what FORM value they might be talking about. I started commenting out all the code I had just put in until I narrowed it down to this code:
Launch code in new window » Download code as text file »
- <input
- type="text"
- name="usage_cap_time"
- value="#FORM.usage_cap_time#"
- />
Ahhh, then it hit me. TIME. This form field ends with the word "Time." This has to be one of ColdFusion's worst features every brought / kept into existence; because this form field ends with "time," ColdFusion will try to validate the form field "usage_cap" as being a valid time value.
Does anyone even use this ColdFusion validation style? How do you sleep at night :)
Download Code Snippet ZIP File
Comments (12) | Post Comment | Ask Ben | Permalink | Print Page
Michael Dinowitz Application.cfc Presentation At NYCFUG - Past, Present, Future
Learning ColdFusion 8: CFImage Part I - Reading And Writing Images
Reader Comments
It's not "time" - it's "_time"
Solution - use camelCase not underscores :)
Posted by todd sharp on Jun 12, 2007 at 10:15 AM
Yeah, there are a few of those that trigger the autovalidation. Like _required for example.
We should have asked for an application-wide setting to disable that 'feature'.
I haven't seen anyone actually use the convention validation, I have seen folks spend a lot of time trying to diagnose the resulting, and unintentional, error.
Put it in the same bucket as <cfinsert> and <cfupdate>
Posted by Dan Wilson on Jun 12, 2007 at 10:17 AM
Crazy! I didn't realize it would even do that for an INPUT tag. I thought it only matters if you use CFINPUT / CFFORM.
Posted by Jason Troy on Jun 12, 2007 at 12:43 PM
Yeah it is crazy :) I think was left over from the days before any real validation was available or something. I think it is time that ColdFusion dumped this from its backwards-compatability.
Posted by Ben Nadel on Jun 12, 2007 at 12:50 PM
Yes and _required and _numeric have caught me in the past when just using the names that someone else used for data in the database!!
Took me hours to debug the first time. Now I warn all students who attend my calsses so that hopefully it won't get them too.
Posted by Kevin Roche on Jun 12, 2007 at 12:52 PM
Here's a funny couple ones, try _applied or _employed. Those seem to fail for me no matter what. I definitely agree that this is as dumb of a feature as building an application server on java (I have to restart it or close file handles just to modify .html files.) The development cycle of using coldfusion is hilarious compared to more professional solutions.
Posted by Xedecimal on Dec 2, 2007 at 10:02 AM
@Xedecimal,
That is so crazy that those would fail. They don't even make sense (from a validation standpoint).
Posted by Ben Nadel on Dec 2, 2007 at 6:12 PM
I asked around for some kind of reference to a list of these 'dumb' names. It was suggested that they don't even have a list of them. I dug around for a while and found these urls...
http://www.chapter31.com/2007/04/24/unwanted-coldfusion-form-validation/
http://cfsilence.com/blog/client/index.cfm/2007/2/27/cfform-Server-Side-Validation-Gotcha
http://www.mischefamily.com/nathan/index.cfm/2007/7/21/ColdFusions-Serverside-Form-Validation
http://livedocs.adobe.com/coldfusion/7/htmldocs/wwhelp/wwhimpl/common/html/wwhelp.htm?context=ColdFusion_Documentation&file=00001385.htm
So this isn't the only place having a blast with this error. Maybe the new Adobe purchase of the good stuff as well as the bad stuff *cough*coldfusion*cough* will allow them to make it better, ha, ha ha, that's funny.
Posted by Xedecimal on Dec 3, 2007 at 2:15 AM
@Xedecimal,
That list on the LiveDocs is pretty big. They really just need to get rid of this feature altogether or just use the _cfformurl style notation that won't be confused with other valid field names.
Posted by Ben Nadel on Dec 3, 2007 at 7:12 AM
It's not just the "time" I had fields ending in "date","creditcard", "digits", etc... and each one of those had the same thing trailed by a "_msg". I cured the problem by ending the value form element with an "_1" and the message form element with a "_2" just so that it was easy to process the forms with the message for each one. This is for a jQuery validation generator that i'm working on that allows you to go through a gui to build your validation and to override the built in validation.
Either way, i know if i see this sucker come up again that it has to do with the naming convention.
You saved me time with this post, thank you!
Posted by HJaber on Mar 6, 2008 at 10:48 AM
Thanks so much for your post. I've been debugging a related error for about two hours now. It was especially odd in that I had two fields, START_NOTICE and START_NOTICE_TIME. Two fields, one with a date and one with the time. Well, for some strange reason, my field START_NOTICE starts taking on the value of "0" and spitting out "1899-12-30" in the FORM scope! After reading this post, I changed the name of START_NOTICE_TIME to START_NOTICETIME and it just all worked! Somehow the validation on the time field was affecting the related field START_NOTICE. I think that is even stranger than the problem with the "_time" in the field name. At least it has stopped. :-)
Posted by Brad Melendy on Apr 30, 2008 at 7:11 PM
@Brad,
Yeah, that's some old-school, built-in validation. Nobody likes it; I am not sure why it is even still part of ColdFusion.
Posted by Ben Nadel on May 1, 2008 at 7:27 AM
