How is the order of the elements in #FORM.fieldNames# determined? Could it be
different and not well structured?
Like if I have a form with text inputs named foo1, foo2, foo3.
Will #FORM.fieldNames# always be:
Foo1,foo2,foo3?
Or could it be ordered different?
Thanks,
Chad
:
How is the order of the elements in #FORM.fieldNames# determined? Could it
be different and not well structured?
Like if I have a form with text inputs named foo1, foo2, foo3.
Will #FORM.fieldNames# always be:
Foo1,foo2,foo3?
Or could it be ordered different?
Thanks,
Chad
of the elements in #FORM.fieldNames# determined? Could
it be different and not well structured?
Like if I have a form with text inputs named foo1, foo2, foo3.
Will #FORM.fieldNames# always be:
Foo1,foo2,foo3?
Or could it be ordered different?
Thanks,
Chad
Thanks for the insight guys.
I will use listSort() before processing the form.FieldNames. This is better
than relying on DOMs and such to do the ordering.
Chad
-Original Message-
From: Qing Xia [mailto:txiasum...@gmail.com]
Sent: Thursday, January 07, 2010 11:42 AM
To: cf-talk
How is the order of the elements in #FORM.fieldNames# determined? Could it
be different and not well structured?
Like if I have a form with text inputs named foo1, foo2, foo3.
Will #FORM.fieldNames# always be:
Foo1,foo2,foo3?
Or could it be ordered different?
Structures
Hello all!
I'm trying to generate a custom error page of type request and still obtain
the form.fieldnames. Is it possible to get the information from the parent
page once the error page has been called?
Thanks!
~|
Want
I'm trying to generate a custom error page of type request and still obtain
the
form.fieldnames. Is it possible to get the information from the parent page
once the
error page has been called?
No, the Form scope is unavailable in an error page when you use
TYPE=REQUEST. I would recommend
I am building binamic survey . SO when i inserti g the value of the radio
buttons all works, but when i am trying to get the id of the textarea it does
not .
I do not know what to do next
CFLOOP LIST=#Form.fieldnames# Index=field
cfif #field# neq btnSubmitSurvey
to: www.winninginthemargins.com
Enter passkey: goldengrove
Web Developer
http://William.Seiter.com
-Original Message-
From: Ron Eis [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 05, 2008 6:57 PM
To: CF-Talk
Subject: RE: using form.fieldNames and CFLOOP to insert selected radio but
tons
I
I agree Dave.
That's why I posted the question here.
I would really appreciate any concrete solutions/options/direction from
the other experts here.
Whenever I have radio buttons I need to read, I just create fieldnames you can
pick up on, like this
name=readThis_field
When you process it,
this
by not including verything on the same page (which for me is easier
organized) and to run my loop and insert in a new page? Is this the best
option?
Is using form.fieldNames the best way to retrieve the selected values
from the form? If so, I'll add the conditional logic as Dave suggested.
I
PERFECT SOLUTION! Thanks Dave and everyone.
Here's what I ended up with:
cfif isDefined(form.inputButton)
cfloop index=i list=#form.fieldNames#
cfif #i# NEQ inputButton
cfquery datasource=#dbname# name=addContact
INSERT INTO contact
(contactDbId
passkey: goldengrove
Web Developer
http://William.Seiter.com
-Original Message-
From: Ron Eis [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 06, 2008 6:37 AM
To: CF-Talk
Subject: RE: using form.fieldNames and CFLOOP to insert selected radio
buttons
Thanks again William and Dave!
I
-Original Message-
From: William Seiter [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 06, 2008 10:54 AM
To: CF-Talk
Subject: RE: using form.fieldNames and CFLOOP to insert selected radio
buttons
Ron,
Since you know what the name of the submit button is on the receiving page,
you can check
Thanks for following up!
I'm always looking for tips and tricks for steamlining my code so I
really appreciate all the information.
-Original Message-
From: William Seiter [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 06, 2008 12:58 PM
To: CF-Talk
Subject: RE: using form.fieldNames
Thanks for following up!
I'm always looking for tips and tricks for steamlining my code so I
really appreciate all the information.
-Original Message-
From: William Seiter [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 06, 2008 12:58 PM
To: CF-Talk
Subject: RE: using form.fieldNames
Here's what I ended up with:
cfif isDefined(form.inputButton)
Just to add to this a bit, you might not want to use the submit button as a
flag, since it's possible in many cases to submit a form without actually
clicking on the submit button, in which case you wouldn't have a
corresponding
I'm trying to insert the value of selected radio buttons using CFLOOP
and #form.fieldNames#.
It's returning the correct values that need to be inserted into the
database, but it's also returning the value and name of my submit
button.
I thought using form.fieldNames was correct but I'm not sure
It's returning the correct values that need to be inserted into the
database, but it's also returning the value and name of my submit
button. I thought using form.fieldNames was correct but I'm not sure
how to return all the selected fields but not the submit? Thanks for any
help!
CF has
form.fieldNames and CFLOOP to insert selected radio
but tons
It's returning the correct values that need to be inserted into the
database, but it's also returning the value and name of my submit
button. I thought using form.fieldNames was correct but I'm not sure
how to return all the selected
as you can get, without
me writing the code. Did you try either?
The first would involve wrapping your CFQUERY with CFIF tags:
cfloop index=i list=#form.fieldNames#
cfif i is not inputbutton
cfquery datasource=#dbname# name=addContact
INSERT INTO contact
MX 6.1 here
I've got a page with a lengthy form (40+ fields). On submit, some of the
fields aren't getting saved to the db. So I start testing:
1) I dump the form structure, fields are there.
2) I dump Form.fieldnames, fields are NOT there.
3) I loop over Form.fieldnames to test and indeed
://www.shayna.com/index.cfm?fuseaction=training.syllabus_displayid=1
-Original Message-
From: Andy Matthews [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 19, 2006 4:49 PM
To: CF-Talk
Subject: Form.fieldnames doesn't contains all form field names?
MX 6.1 here
I've got a page with a lengthy
dumping the form structure will also contain the 'fieldnames' key, as
well as 'x' and 'y' (i believe).
On 7/19/06, Andy Matthews [EMAIL PROTECTED] wrote:
Just an update. Form.fieldnames contains 45 items whereas dumping the FORM
structure shows 48. Is there a limit to the form scope
FORM will only contain x and y if you've used an image button.
Regardless, there are several fields contained in the FORM scope that aren't
in the form.fieldnames variable.
Sandra, no such luck...all fields are text fields.
!//--
andy matthews
web developer
certified
in the form.fieldnames variable.
Sandra, no such luck...all fields are text fields.
!//--
andy matthews
web developer
certified advanced coldfusion programmer
ICGLink, Inc.
[EMAIL PROTECTED]
615.370.1530 x737
--//-
-Original Message-
From: Charlie Griefer
[EMAIL PROTECTED] wrote:
FORM will only contain x and y if you've used an image button.
Regardless, there are several fields contained in the FORM scope that aren't
in the form.fieldnames variable.
Sandra, no such luck...all fields are text fields.
!//--
andy
Any fields with duplicate names? That might mess things up.
-- Josh
- Original Message -
From: Andy Matthews [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Wednesday, July 19, 2006 1:49 PM
Subject: Form.fieldnames doesn't contains all form field names?
MX 6.1 here
Those show up as a comma delimited list.
-Original Message-
From: Josh Nathanson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 19, 2006 5:21 PM
To: CF-Talk
Subject: Re: Form.fieldnames doesn't contains all form field names?
Any fields with duplicate names? That might mess
What are the types of the problematic form fields?
What are the names of the problematic form fields?
~Brad
-Original Message-
From: Andy Matthews [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 19, 2006 3:49 PM
To: CF-Talk
Subject: Form.fieldnames doesn't contains all form field names
, July 19, 2006 2:27 PM
Subject: RE: Form.fieldnames doesn't contains all form field names?
Those show up as a comma delimited list.
-Original Message-
From: Josh Nathanson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 19, 2006 5:21 PM
To: CF-Talk
Subject: Re: Form.fieldnames doesn't
The name shows up just the one time.
-Original Message-
From: Josh Nathanson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 19, 2006 5:35 PM
To: CF-Talk
Subject: Re: Form.fieldnames doesn't contains all form field names?
The values of the duplicate fields would show up as a comma
Here's the list of what's showing up where. Am I missing something?
FORM|fieldnames
---
amount_purchased|amount_purchased
assetform_savings
OK, so that could cause the problem he's having. He said there seem to be
field names missing from the form.fieldnames list. If he has three fields
with the same name, there will seem to be two less names in
form.fieldnames than there are fields on the submitted form. Although,
that would
]
Sent: Wednesday, July 19, 2006 5:51 PM
To: CF-Talk
Subject: RE: Form.fieldnames doesn't contains all form field names?
Here's the list of what's showing up where. Am I missing something?
FORM|fieldnames
Becarefull of the reserved validation strings that are appended to field names
such as _date. These strings cause ColdFusion to treat the form field as a
validation of another form field.
Full list here:
http://livedocs.macromedia.com/coldfusion/7/htmldocs/wwhelp/wwhimpl/js/html/wwhelp.htm
having. He said there seem to be
field names missing from the form.fieldnames list. If he has three fields
with the same name, there will seem to be two less names in
form.fieldnames than there are fields on the submitted form. Although,
that would be pretty easy to diagnose, so that's probably
the form.fieldnames list. If he has three
fields
with the same name, there will seem to be two less names in
form.fieldnames than there are fields on the submitted form. Although,
that would be pretty easy to diagnose, so that's probably not the issue.
-- Josh
- Original Message -
From
/wwhimpl/js/html/wwhelp.htm
OK, so that could cause the problem he's having. He said there seem to be
field names missing from the form.fieldnames list. If he has three fields
with the same name, there will seem to be two less names in
form.fieldnames than there are fields on the submitted form
Here is a weird one unless I am missing something.
I have a form with lots and lots of checkboxes, three of them are
sh_buy_c_date,sh_sel_c_date,sh_mkt_time
all three are checkboxes. I check ALL checkboxes on the form, submit it,
loop over form.fieldnames list, the above three
-Original Message-
From: Brian Dumbledore [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 27, 2006 5:20 PM
To: CF-Talk
Subject: form.fieldnames does not bring all values.
Here is a weird one unless I am missing something.
I have a form with lots and lots of checkboxes, three of them
am missing something.
I have a form with lots and lots of checkboxes, three of them are
sh_buy_c_date,sh_sel_c_date,sh_mkt_time
all three are checkboxes. I check ALL checkboxes on the form, submit it,
loop over form.fieldnames list, the above three are not in the list. However,
when I do
10001
212.691.1134 x 14
212.691.3477 fax
www.nylontechnology.com
Some people call me the space cowboy. Some people call me the gangster of
love.
-Original Message-
From: Brian Dumbledore [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 27, 2006 5:20 PM
To: CF-Talk
Subject: form.fieldnames
Thanks to everyone for the links and explanation. Yes, I had _date
in the fieldnames, so that's the answer.
~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting
Just curious if anyone else has experienced this:
I was looping over the fields of a submitted form using the
Form.Fieldnames variable, and I noticed that there were missing
fieldnames.
When I looped over StructKeyList(form), the fieldnames were all there.
I couldn't find any commonality among
?
Ray
Tom McNeer wrote:
Just curious if anyone else has experienced this:
I was looping over the fields of a submitted form using the
Form.Fieldnames variable, and I noticed that there were missing
fieldnames.
When I looped over StructKeyList(form), the fieldnames were all there.
I
Sacramento, CA
C code. C code run. Run code run. Please!
- Cynthia Dunning
-Original Message-
From: Ray Champagne [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 04, 2005 1:44 PM
To: CF-Talk
Subject: Re: Missing value in the Form.Fieldnames variable
If the word
I have noticed this too
Form.Fieldnames variable gives wrong results if you have a field name that
ends with date. So if you have a field called s_date - the
form.FIELDNAMES variable will not have that as a value.
Looks like a bug... i just renamed my fields and it worked.
DK
-Original
]
Sent: Thursday, August 04, 2005 2:04 PM
To: CF-Talk
Subject: RE: Missing value in the Form.Fieldnames variable
I have noticed this too
Form.Fieldnames variable gives wrong results if you have a field name
that
ends with date. So if you have a field called
Yeah, I know Hes back again :-)
Anyways, Im trying loop over a set of form fields, stopping the loop when I
hit a specific blank field. (This field is automatically populated from another
form for each record the user wants to insert, it could be 1 it could be as
many as 9.
There
Scott,
Maybe give:
cfif structKeyExists(attributes, invoice
i),#attributes[invoice i]#/cfif
a whirl?
Cheers,
Joe
On 5/13/05, SStewart [EMAIL PROTECTED] wrote:
Yeah, I know He's back again :-)
Anyways, I'm trying loop over a set of form fields, stopping the loop when I
hit a specific
Quotes look messed up, and do you really want the condition to be neq '?
Yeah, I know ?He?s back again? :-)
Anyways, I?m trying loop over a set of form fields, stopping the loop
when I hit a specific blank field. (This field is automatically
populated from another form for each record the
Maybe give:
cfif structKeyExists(attributes, invoice
i),#attributes[invoice i]#/cfif
a whirl?
Cheers,
~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting
: Friday, May 13, 2005 01:26 pm
To: CF-Talk
Subject: Re: Looping over Form.Fieldnames
Importance: Low
Maybe give:
cfif structKeyExists(attributes, invoice
i),#attributes[invoice i]#/cfif
a whirl?
Cheers,
~|
Logware
__
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 2:02 PM
To: CF-Talk
Subject: RE: Emailing Form.FieldNames results via looping?
if I remember correctly, #form[thisField]# won't work in
cf5, but I'm not 100% sure of that (It's been so long since
list=#Form.FieldNames#
cfoutput#thisField#: #Evaluate(thisField)#br/cfoutput
/cfloop
That code outputs what I want but I can't use it within a CFMAIL tag
because I get this error:
A CFOUTPUT tag is nested inside a CFMAIL tag with no GROUP= or QUERY=
attributes . This is not allowed.
Do I need
Bob,
Inside your cfmail tags, you only need to use this code:
cfloop index=thisField list=#Form.FieldNames#
#thisField#: #evaluate(thisField)#br
/cfloop
(just remove the cfoutputs)
Steve
-Original Message-
From: Bob Haroche [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18
Get rid of the cfoutputs and it'll work :-)
Matt Robertson [EMAIL PROTECTED]
MSB Designs, Inc.http://mysecretbase.com
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User
You don't need CFOUTPUT inside of CFMAIL.Second, skip the evaluate and just
use #form[thisField]#
Andy
-Original Message-
From: Bob Haroche [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 12:24 PM
To: CF-Talk
Subject: Emailing Form.FieldNames results via looping?
I have a form
Form.FieldNames results via looping?
You don't need CFOUTPUT inside of CFMAIL.Second, skip the evaluate and
just
use #form[thisField]#
Andy
-Original Message-
From: Bob Haroche [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 12:24 PM
To: CF-Talk
Subject: Emailing Form.FieldNames results
if I remember correctly, #form[thisField]# won't work in
cf5, but I'm not 100% sure of that (It's been so long since
I used CF5).
I'm pretty sure that syntax will work in CF 4 and up.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays
Andy Ousterhout wrote:
You don't need CFOUTPUT inside of CFMAIL.Second, skip the
evaluate and just
use #form[thisField]#
Thanks so much to both responeders. I had the dreaded Evaluate in
there b/c I grabbed the code from the O'Reilly Programming CF book.
I'll try without it.
Regards,
Bob
Dave watts wrote:
I'm pretty sure that syntax will work in CF 4 and up.
Would it work for other scopes as well?i.e. #client[blah]#.I've got
an app that has a boatload of evaluates that I would love to clean up,
but have left alone so it doesn't break on older CFs.
Yup, all your fav scopes.Form, URL, Variables(cf6+), Session, Client, Application and Server ...
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
If it works for form, it will work for all scopes.Just try it.
-Original Message-
From: Matt Robertson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 3:11 PM
To: CF-Talk
Subject: RE: Emailing Form.FieldNames results via looping?
Dave watts wrote:
I'm pretty sure that syntax
I'm pretty sure that syntax will work in CF 4 and up.
Would it work for other scopes as well?i.e. #client[blah]#.
I've got an app that has a boatload of evaluates that I
would love to clean up, but have left alone so it doesn't
break on older CFs.
It will depend on what version, and for
Thx Dave,
The app does work well as is and, if it ain't broke...
Matt Robertson [EMAIL PROTECTED]
MSB Designs, Inc.http://mysecretbase.com
[Todays Threads]
[This Message]
[Subscription]
[Fast
break it!:-)
-Original Message-
From: Matt Robertson [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 5:27 PM
To: CF-Talk
Subject: RE: Emailing Form.FieldNames results via looping?
Thx Dave,
The app does work well as is and, if it ain't broke
Gregory I. Hayes wrote:
Ok, what happened? I used to be able to loop through form.fieldnames to
create a list of all of the fields and then I could write my processor
script. CFMX, on the other hand, gives me the following:
Element FIELDNAMES is undefined in FORM.
Anybody have any ideas
Ok, what happened? I used to be able to loop through form.fieldnames to
create a list of all of the fields and then I could write my processor
script. CFMX, on the other hand, gives me the following:
Element FIELDNAMES is undefined in FORM.
Anybody have any ideas?
Cutter
Ok, what happened? I used to be able to loop through
form.fieldnames
Try structkeylist(form)
Tim.
---
OUR NEW SITE IS NOW LIVE
Visit our new website at http://www.rawnet.com/ and
race around the beautiful Bracknell streets at
http
Turn on Display Variables in CF Admin and see what is getting passed
-Original Message-
From: Cutter (CF_Talk) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:29 AM
To: CF-Talk
Subject: Form.Fieldnames and MX
Ok, what happened? I used to be able to loop through
Can you turn on debugging? If so, what does the debugger window tell you
about the Form variables in the Scope Variables section?
- Jim
-Original Message-
From: Cutter (CF_Talk) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:29 AM
To: CF-Talk
Subject: Form.Fieldnames
happened? I used to be able to loop through
form.fieldnames
Try structkeylist(form)
Tim.
---
OUR NEW SITE IS NOW LIVE
Visit our new website at http://www.rawnet.com/ and
race around the beautiful Bracknell streets at
http
(CF_Talk) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:29 AM
To: CF-Talk
Subject: Form.Fieldnames and MX
Ok, what happened? I used to be able to loop through form.fieldnames to
create a list of all of the fields and then I could write my processor
script. CFMX, on the other hand
in CF Admin and see what is getting
passed
-Original Message-
From: Cutter (CF_Talk) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:29 AM
To: CF-Talk
Subject: Form.Fieldnames and MX
Ok, what happened? I used to be able to loop through form.fieldnames
to
create a list
, February 13, 2003 9:26 AM
To: CF-Talk
Subject: Re: Form.Fieldnames and MX
Though Form is selected for Display, nothing for Form is coming up on
the action page in the debugging info. (Maybe because no data is being
passed?)
Cutter
Andy Ousterhout wrote:
Turn on Display Variables in CF Admin
Ok, what happened? I used to be able to loop through
form.fieldnames to create a list of all of the fields
and then I could write my processor script. CFMX, on
the other hand, gives me the following:
Element FIELDNAMES is undefined in FORM.
This variable still exists in CFMX, whenever
?)
Cutter
Andy Ousterhout wrote:
Turn on Display Variables in CF Admin and see what is getting
passed
-Original Message-
From: Cutter (CF_Talk) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:29 AM
To: CF-Talk
Subject: Form.Fieldnames and MX
Ok, what
:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 9:42 AM
To: CF-Talk
Subject: RE: Form.Fieldnames and MX
Ok, what happened? I used to be able to loop through
form.fieldnames to create a list of all of the fields
and then I could write my processor script. CFMX, on
the other hand, gives me
:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 10:41 AM
To: CF-Talk
Subject: Re: Form.Fieldnames and MX
Yes, method=post
Cutter
Willy Ray wrote:
You sure your method attribute is set to 'POST'?
[EMAIL PROTECTED] 02/13/03 08:26AM
Though Form is selected for Display, nothing
-Original Message-
From: Cutter (CF_Talk) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 8:29 AM
To: CF-Talk
Subject: Form.Fieldnames and MX
Ok, what happened? I used to be able to loop through form.fieldnames
to
create a list of all of the fields and then I could write my
that a recent updater may have fixed this problem, but not
sure.
E. Keith Dodd
Wings of Eagles Services
www.wingserv.com
- Original Message -
From: Justin Hansen [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 10:36 AM
Subject: RE: Form.Fieldnames and MX
I had
Form.FieldNames in the order in which they were
created and not in All Uppercase.
Stephen
Also - I'd avoid using this variable for the sake of future
compatibility. It has the feel of something that might to be
depricated. Now that the FORM scope is a structure, the fieldnames
variable
Wouldn't #form.fieldnames# return all the fields? i mean what if there were
some other fields that was passed through but not related to form.section
this would work.
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 27, 2002 3:21 PM
To: CF-Talk
#form.fieldnames# woudl return
section1,section2,section3,section4
Wouldn't #form.fieldnames# return all the fields?
Yes, it would. The original poster said that in his case, those fields were
section1,section2,section3,section4.
Dave Watts, CTO, Fig Leaf Software
http
need to
change Form.field3 to = 4). Using CFSET I can't use a function on the left
side of the = CFSET (Listgetat(Form.fieldnames, count) = 4. I can't hard
code it because the fieldnames are drawn from a database and change depending
on what itemthe form is built for.
Any suggestions?
Ian
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--_=_NextPart_001_01C019DD.E44CBCB8
Content-Type: text/plain;
charset="iso-8859-1"
cfset formField = Listgetat(Form.fieldnames, co
1) If you don't put METHOD="post" (I suppose METHOD="get"
works too) in your opening FORM tag, the form variables get
passed in the URL instead of the form. Goofy, huh?
If you use METHOD="GET", your variables will be passed via the URL.
Variables within the Form scope have been received from
Thanks for the insight, Dave. I've just always used POST, and I know there
are some cases when you want to use GET, but I'm not clear on why. What's
the difference? (In practical terms, that is).
Regards,
Karl Simanonok
Dave Watts wrote:
1) If you don't put METHOD="post" (I suppose
Thanks for the insight, Dave. I've just always used POST,
and I know there are some cases when you want to use GET, but
I'm not clear on why. What's the difference? (In practical
terms, that is).
If you're passing small amounts of data back to the server, a GET request is
simpler for that
RE: Form.Fieldnames Missing
Is there a reason why the form.fieldnames field would not be
passed in a form?
I vaguely seem to recall that in some versions of CF prior to 4.5.x, if
the
ENCTYPE attribute of the form is set to "multipart/form-data", which is
what
you'd use for file uplo
I can recreate the error if the only form elements that are named are
checkboxes and radio buttons, and none of them have been checked or
selected. At that point form.fieldnames is not defined in the action page.
Any chance your form only has checkboxes and radio buttons?
Dan
-Original
cc:
Subject: RE: Form.Fieldnames Missing
I can recreate the error if the only form elements that are named are
checkboxes and radio buttons, and none of them have been checked or
selected. At that point form.fieldnames is not defined in the action
page.
Any chance your for
Is there a reason why the form.fieldnames field would not be
passed in a form?
...
I vaguely seem to recall that in some versions of CF prior to
4.5.x, if the ENCTYPE attribute of the form is set to
"multipart/form-data", which is what you'd use for file uploads,
FORM.
We'd love to hear the solution . . . I'm sure this will be on Michael's next
test . . .
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 12, 2000 10:26 AM
To: [EMAIL PROTECTED]
Subject: RE: Form.Fieldnames Missing
While the form isn't only
TECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Form.Fieldnames Missing
Message-ID: 001001bfebb2$93c4af70$[EMAIL PROTECTED]
Is there a reason why the form.fieldnames field would not be
passed in a form?
I vaguely seem to recall that in some versions of CF prior to 4.5.x, if
Are you sure you used method="post"? If you forgot to add that, you wouldn't
have the fieldnames in the debugging.
-d
Deanna Schneider
Interactive Media Developer
UWEX Cooperative Extension Electronic Publishing Group
103 Extension
Your 3rd form has a field called UW_NOD_RESCIND_DATE that would never get
passed IF form.fieldnames was passed (_date, _integer, _float, _time,
_range, _eurodate are all naming convention to form inputs that will cause
server side validation). That doesn't explain why the form.fieldnames never
Is there a reason why the form.fieldnames field would not be
passed in a form?
I vaguely seem to recall that in some versions of CF prior to 4.5.x, if the
ENCTYPE attribute of the form is set to "multipart/form-data", which is what
you'd use for file uploads, FORM.FIELDNAMES would
1 - 100 of 108 matches
Mail list logo
