The debate on client-side vs. server-side form validation is ongoing.
Client-side is more responsive, and attempts to keep bad data from
ever reaching your application, but relies on javascript being
enabled. Since this is something easily turned off by users, one can't
always rely on it to do form validation. So server-side validation is
needed as well to allow your full application to gracefully degrade in
the absence of working javascript on the client's side. Coding
defensively helps!
On Sep 11, 2010, at 10:55 AM, tedd wrote:
At 9:49 AM -0400 9/11/10, Jason Pruim wrote:
Hey everyone!
Hope you are having a great weekend, and I'm hoping someone might
be coherent enough to help me find a more elegant solution to a
problem that I have...
I have a form for submitting an event to a website, and if the form
is not submitted successfully (such as they didn't fill out a
required field) I want it to redisplay the form with inline errors
as to what happened and display the values they selected...
-snip-
Any ideas what I'm missing?
Jason:
I think what you are missing is that this data collection should be
split between client-side and server-side operations.
For client-side simply use javascript to monitor what they user
enters and then immediately respond to the requirements imposed upon
the user.
After the user fills out the information correctly and clicks
submit, then have your server-side scripts check the data again and
respond accordingly.
Here are a couple of examples:
http://webbytedd.com/c/form-calc/
http://webbytedd.com/c/form-submit/
Cheers,
tedd
--
-------
http://sperling.com/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
