• My form is not working
• Relative links stop working after form is submitted
• More information - Forms Tutorial

User ID not set correctly Many times the userid value in the hidden field does not reflect the userid of the account on which the form resides. For instance, many times clients use one of WebCom's template form config files where the userid hidden field line reads:

<INPUT TYPE=hidden NAME=userid VALUE=webcom>

and neglect to change 'webcom' in the above tag to the userid for their account. For example, if your userid is coolpage then you want the tag to read:

<INPUT TYPE=hidden NAME=userid VALUE=coolpage>

This tells the forms processor which account is using this form, and in which account to look for the configuration file.
Form name not set correctly The value in the form_name hidden field must match the name of the configuration file for that form. Or, if you intend to have no configuration file for that form, the value there must not match any file which is in the form directory off of the root directory of your account. For example, if you have a form which you wish to have reference a config file named order.cfg, then the hidden field should look like this:

<INPUT TYPE=hidden NAME=form_name VALUE=order>

Many times when the data from a form is not being processed and routed as the user intends, the problem is simply that the value for form_name does not match the correct configuration file.
Repeating field values If it appears that some of the data fields are not being emailed or routed to the intended destination, there maybe more than one input field using the same variable name. Sometimes a form will have several fields in the same form with the same name, i.e. quantity, price, etc. Each input field must have unique names so that the forms processor can differentiate between each piece of data and handle it accordingly.

Field variable starting with a non-alpha character If you have any field variables in a form that begin with anything except a letter ("2_quant", for example) the forms processor will return an error. Such field names are not allowed.

Relative links stop working after form is submitted

If a special screen has been designed to appear after a form submission, relative links to pictures and in hyperlink references will suddenly not work. This is because, as you can observe, the address that appears in the URL box of a browser of any form submission confirmation screen is http://webcom.com/~webcom/cgi-bin/form. Thus, relative links would use this as their base.

To overcome this problem, place a <BASE HREF> tag in the HEAD section of the confirmation page, such as:

<BASE HREF="http://webcom.com/~webcom/userid/path/filename.shtml">

For more information, see the full documentation on theForms Processor, or go for a guided tour of how to create forms with our Forms Tutorial.