Listen Live
|
||
| Mountain Area Information Network | ||
|
Help adding fill-in forms to webpages So, you are ready to interact with your users, instead of just sending them information. You are ready to get flooded with input from your users, beyond the <b> mailto:</b> link. Maybe you want to have a survey online, or let people join your mailing list. Either way, we can accomplish this with FormMail. FormMail is a program that runs on MAIN's computers that takes the data from the form in your HTML page, formats it into a readable email and sends it to any address(s) you want it to go to. The FormMail program on MAIN is pretty much an industry standard for doing this. Formmail is available at http://nms-cgi.sourceforge.net/ . Most of this help page has been taken from the README file. The most important tags in your form is the . To make FormMail work, your form tag should read:and end with after all is said and done. You will also need to include a submit button, which you can include as: There is only one form field that you must have in your form, for FormMail to work correctly. This is the recipient field.
Field: recipient
Description: This form field allows you to specify to whom you wish for your form results to be mailed. Most likely you will want to configure this option as a hidden form field with a value equal to that of your e-mail address. Syntax: Field: subject Description: The subject field will allow you to specify the subject that you wish to appear in the e-mail that is sent to you after this form has been filled out. If you do not have this option turned on, then the script will default to a message subject: WWW Form Submission Syntax: If you wish to choose what the subject is: Field: email Description: This form field will allow the user to specify their return e-mail address. If you want to be able to return e-mail to your user, I strongly suggest that you include this form field and allow them to fill it in. This will be put into the From: field of the message you receive. If you want to require an email address with valid syntax, add this field name to the 'required' field. Syntax: Field: realname Description: The realname form field will allow the user to input their real name. This field is useful for identification purposes and will also be put into the From: line of your message header. Syntax:
Field: redirect Description: If you wish to redirect the user to a different URL, rather than having them see the default response to the fill-out form, you can use this hidden variable to send them to a pre-made HTML page. Syntax: To choose the URL they will end up at: Field: required Description: You can now require for certain fields in your form to be filled in before the user can successfully submit the form. Simply place all field names that you want to be mandatory into this field. If the required fields are not filled in, the user will be notified of what they need to fill in, and a link back to the form they just submitted will be provided. Syntax: If you want to require that they fill in the email and phone fields in your form, so that you can reach them once you have received the mail, use a syntax like: Field: env_report Description: Allows you to have Environment variables included in the e-mail message you receive after a user has filled out your form. Useful if you wish to know what browser they were using, what domain they were coming from or any other attributes associated with environment variables. The following is a short list of valid environment variables that might be useful: Syntax: If you wanted to find the remote host and browser sending the request, you would put the following into your form: Field: sort Description: This field allows you to choose the order in which you wish for your variables to appear in the e-mail that FormMail generates. You can choose to have the field sorted alphabetically or specify a set order in which you want the fields to appear in your mail message. By leaving this field out, the order will simply default to the order in which the browsers sends the information to the script (which is usually the exact same order as they appeared in the form.) When sorting by a set order of fields, you should include the phrase "order:" as the first part of your value for the sort field, and then follow that with the field names you want to be listed in the e-mail message, separated by commas. Version 1.6 (MAIN's Version) allows a little more flexibility in the listing of ordered fields, in that you can include spaces and line breaks in the field without it messing up the sort. This is helpful when you have many form fields and need to insert a line wrap. Syntax: To sort alphabetically: Field: print_config Description: print_config allows you to specify which of the config variables you would like to have printed in your e-mail message. By default, no config fields are printed to your e-mail. This is because the important form fields, like email, subject, etc. are included in the header of the message. However some users have asked for this option so they can have these fields printed in the body of the message. The config fields that you wish to have printed should be in the value attribute of your input tag separated by commas. Syntax: If you want to print the email and subject fields in the body of your message, you would place the following form tag: Field: print_blank_fields Description: print_blank_fields allows you to request that all form fields are printed in the return HTML, regardless of whether or not they were filled in. FormMail defaults to turning this off, so that unused form fields aren't e-mailed. Syntax: If you want to print all blank fields: Field: title Description: This form field allows you to specify the title and header that will appear on the resulting page if you do not specify a redirect URL. Syntax:
If you wanted a title of 'Feedback Form Results': Field: return_link_url Description: This field allows you to specify a URL that will appear, as return_link_title, on the following report page. This field will not be used if you have the redirect field set, but it is useful if you allow the user to receive the report on the following page, but want to offer them a way to get back to your main page.Syntax:
Field: return_link_title Description: This is the title that will be used to link the user back to the page you specify with return_link_url. The two fields will be shown on the resulting form page as:Syntax:
Field: missing_fields_redirect Description: This form field allows you to specify a URL that users will be redirected to if there are fields listed in the required form field that are not filled in. This is so you can customize an error page instead of displaying the default.Syntax:
Field: background Description: This form field allow you to specify a background image that will appear if you do not have the redirect field set. This image will appear as the background to the form results page.Syntax:
Field: bgcolor Description: This form field allow you to specify a bgcolor for the form results page in much the way you specify a background image. This field should not be set if the redirect field is.Syntax:
For a background color of White: Field: text_color Description: This field works in the same way as bgcolor, except that it will change the color of your text.Syntax:
For a text color of Black: Field: link_color Description: Changes the color of links on the resulting page. Works in the same way as text_color. Should not be defined if redirect is.Syntax:
For a link color of Red: Field: vlink_color Description: Changes the color of visited links on the resulting page. Works exactly the same as link_color. Should not be set if redirect is.Syntax:
For a visited link color of Blue: Field: alink_color Description: Changes the color of active links on the resulting page. Works exactly the same as link_color. Should not be set if redirect is.Syntax:
For a visited link color of Blue: Wrapping it up |
|
Join us on Facebook
©2014 Mountain Area Information Network
34 Wall St, Suite 407
Asheville, NC 28801
(866) 962-6246 ~ (828) 255-0182
Fax: (828) 254-2286