This is a test please ignore.
thanks,
John
ma...@fusionlink.com
-
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.org/mailinglists
Archive @ http:
What of the AJAX approach to validation? You can pass the form to a server
side object for validation. Take the CF8 feature of cfajaxproxy.
Obviously, you can turn of JavaScript. As well as a client initiated
validation would not solely suffice.
Teddy R. Payne, ACCFD
Google Talk - teddyrpa...@g
And this is why I never use it unless the "user" has their knickers in a wad
to know about the error before they go to the next page. Even then I
usually don't bother (especially if they are on an intranet) because the
server validation is so quick they don't realize that they've just *gasp*
submi
Yes Charlie, but the server side is dependent upon receiving a flag
from the client to tell the server what to validate, if I recall
correctly. So effectively, it is still client-side validation.
-dhs
Dean H. Saxe, CISSP, CEH
d...@fullfrontalnerdity.com
"I have always strenuously supported
Thanks for all that, and fair enough. I missed the looping that was
appending more to the field name, but the info may still help someone.
And indeed what you've confirmed is what I would have said if you'd stopped
at your first paragraph: the onserver validation is causing CF to create the
hi
Hi Charlie,
Thanks for pointing out _date validation. That would make sense. But if you
notice, from the code, I use a loop and I am *appending* the index number
variable #thisrow# to the end of the cfinput absence_date#this_row#. So
technically, CF should not have done the _date validation as you
Just to be clear, Ajas's use of validateat="onblur,onsubmit,onserver" does
in fact do both client- and server-side validation, but no doubt the whole
subject of validation (client and server-side) is indeed important and
deserves careful scrutiny from a security perspective.
On a separate topic,
Ajas, what you're being tripped up by is the fact that you're using a suffix
of _date for your input field. This goes back to an old approach to doing
server-side field validation that's existed for years. The problem is that
CF is being confused by your _date field name (absence_date) and it thi
Absolutely. So its almost useless. ;-)
Dean H. Saxe, CISSP, CEH
d...@fullfrontalnerdity.com
"[U]nconstitutional behavior by the authorities is constrained only by
the peoples' willingness to contest them"
--John Perry Barlow
On Feb 12, 2009, at 11:25 AM, Mischa Uppelschoten ext 10 wrot
: Plus its a completely useless client side check
I use it as an easy way to alert "good" users that they have forgotten to enter
some data, on top of server side validation of course.
/m
-
To unsubscribe from this list, manage your p
Thank you guys.
That was really helpful.
http://ajashadi.blogspot.com
We cannot become what we need to be, remaining what we are.
No matter what, find a way. Because thats what winners do.
You can't improve what you don't measure.
Quality is never an accident; it is always the result of high in
Plus its a completely useless client side check which needs to be
repeated server-side as well if you want any assurance that validation
was successful.
-dhs
Dean H. Saxe, CISSP, CEH
d...@fullfrontalnerdity.com
"If liberty means anything at all, it means the right to tell people
what they
Ajas,
I recommend reading the Adobe Live Docs concerning validation and form
fields. In the below snippet, you will see some curious behavior:
What you will see is that the data will return a string for OnBlur and
OnSubmit validation types, but OnServer is giving you the data exp
As a matter of habit, I do not use the cfinput tags for validation however
the few times I've reviewed or modified code from other developers who
validate dates this way, this is the behavior I have seen.
In general, when I'm checking the date on the submit, I format it
anyway.
On Thu, Feb 12
oyu stll no wut he ment... ;)
From: Dean H. Saxe
To: discussion@acfug.org
Sent: Thursday, February 12, 2009 10:41:36 AM
Subject: Re: [ACFUG Discuss] weird cfinput vs input stuff. date is shown as {d
'2009-02-12'} vs 02/12/2009
Please tell me you mistyped per
Please tell me you mistyped perfect on purpose.
Please.
-dhs
Dean H. Saxe, CISSP, CEH
d...@fullfrontalnerdity.com
"I have always strenuously supported the right of every man to his own
opinion, however different that opinion might be to mine. He who
denies another this right makes a slave
Ajas,
This is my unconfirmed assertion. You have a validator type of type "date",
which returns a string expression of a date object notation. My assertion
is that the validator type that you use will give you the data type on the
submission in its expressed format.
I changed your code to valida
Thanks,
Yes, but the big question is why cffrom cfinput would send date in that
format. Its not the first time I have i used cfinput. Date usually comes
across in standard date format.
Anyone???
http://ajashadi.blogspot.com
We cannot become what we need to be, remaining what we are.
No matter w
Do a dateformat(formfield,'mm/dd/') before using the data from the form.
On Thu, Feb 12, 2009 at 9:41 AM, Ajas Mohammed wrote:
> Hi,
>
> I noticed this in my form submission and dont know why cfinput with
> validation would show date as *{d '2009-02-12'} *whereas regular input
> would show s
Hi,
I noticed this in my form submission and dont know why cfinput with
validation would show date as *{d '2009-02-12'} *whereas regular input would
show same value as* 02/12/2009* . See code below :
so in this form, i entered 02/12/2009 in both the textboxes and i get weird
output.
Any
20 matches
Mail list logo
