Menu
Community /Pin to ProfileBookmark
@NogDogNov 22.2006 — #It's probably easiest to do this by having the form and the form-processing on the same page (therefore the form action points to its own page). Then you can start that page by checking to see if the form has been submitted, typically by checking to see if some $_POST or $_GET value is set (e.g.: [b]if(isset($_POST['fieldname']))[/b]). Within that conditional processing block, you first do your form validation. If everything is OK, then you process the request, output the results (or redirect to a "success" page), and exit. If any errors were detected, you then let it fall out of your conditional block and let the form display. Within the form, you can have conditional statements checking for error conditions you may have trapped in the form validation, and output error messages or other error indicators as desired.@NogDogNov 22.2006 — #Generally, the choice of POST or GET method should be based on whether the request is to do something that is "idempotent" or not:
(From the[url=http://www.w3.org/TR/html4/interact/forms.html#submit-format]w3.org HTML 4.01 specification[/url] .)@NogDogNov 23.2006 — #If you want or need to keep the form and form-handler on different pages and you are using sessions (or can add sessions to it), you can use session variables to store error information. The form-handler can write errors to the $_SESSION array then use header() to redirect back to the form page. The form page can check for errors values in $_SESSION, and if found output them on the page (and then unset them so that they don't persist).
Error checking
Ok im not sure why im drawing such a blank on this but i cant figure it out to save my life.
Basicly I have a form. When users submit the form i want it to check for any blanks and either decline and tell them by a red star next to the field they forgot to imput something.
Any help??
Sign in
to post a comment5 Comments(s) ↴
0
@NogDogNov 22.2006 — #It's probably easiest to do this by having the form and the form-processing on the same page (therefore the form action points to its own page). Then you can start that page by checking to see if the form has been submitted, typically by checking to see if some $_POST or $_GET value is set (e.g.: [b]if(isset($_POST['fieldname']))[/b]). Within that conditional processing block, you first do your form validation. If everything is OK, then you process the request, output the results (or redirect to a "success" page), and exit. If any errors were detected, you then let it fall out of your conditional block and let the form display. Within the form, you can have conditional statements checking for error conditions you may have trapped in the form validation, and output error messages or other error indicators as desired.0
@NogDogNov 22.2006 — #Generally, the choice of POST or GET method should be based on whether the request is to do something that is "idempotent" or not:The "get" method should be used when the form is idempotent (i.e., causes no side-effects). Many database searches have no visible side-effects and make ideal applications for the "get" method.
If the service associated with the processing of a form causes side effects (for example, if the form modifies a database or subscription to a service), the "post" method should be used.
[i]Note. The "get" method restricts form data set values to ASCII characters. Only the "post" method (with enctype="multipart/form-data") is specified to cover the entire [ISO10646] character set.[/i] [Which might therefore be a reason to use POST for certain idempotent requests -- NogDog]
[/quote]
(From the
0
@NogDogNov 23.2006 — #If you want or need to keep the form and form-handler on different pages and you are using sessions (or can add sessions to it), you can use session variables to store error information. The form-handler can write errors to the $_SESSION array then use header() to redirect back to the form page. The form page can check for errors values in $_SESSION, and if found output them on the page (and then unset them so that they don't persist).