This page describes common problems people encounter when using the WebCom Forms Processor, and provides brief answers explaining the probable sources of the problems, with links to further information.

• I've created a form, but I am getting the error message "Not Found".
• I've created a form, but I am getting "Unable to process form: Form owner [or form name] not identified".
• I've created a form, and a configuration file, but the contents of the form are still being mailed to me.
• I've created a form, and a configuration file, but the Forms Processor seems to be ignoring my configuration file.
• I've created a form and a configuration file, but I am getting "Unable to process form: Form is very busy".

• Incorrect ACTION in the opening FORM tag
• Missing/Incorrect in the two required hidden fields
• Missing "form" directory
• Incorrect "form_name"
• Other common problems

Default Form Behavior (when no configuration file is used)

I've created a form, but I am getting the error message "Not Found".

Most likely, the ACTION of your form is incorrect.

I've created a form, but I am getting "Unable to process form: Form owner [or form name] not identified".

Most likely, your form is missing the two required hidden fields.

I've created a form, and a configuration file, but the contents of the form are still being mailed to me,
or
I've created a form, and a configuration file,

but the Forms Processor seems to be ignoring my configuration file.

Most likely, the WebCom Forms Processor is not finding your configuration file, because you have not created a "form" directory, or have placed the configuration ("form_name.cfg") file in an incorrect location.

Another possible source of this problem is when your form contains an incorrect "form_name".

This happens when you try to use a file parameter or a format file statement to write to a file that does not or cannot exist. For instance, if you were trying to write to a file "www/files/file.ext" when the 'files/' directory does not exist in your file structure. If you get this error message, make sure that your file parameter or format file statements are correct. Keep in mind that the form processor operates from the home directory of your Webcom account, so paths to files in your website should start with "www/".

Any Form using these the WebCom Forms Processor or Glimpse Indexing must use the following syntax for the ACTION parameter:

• WebCom Forms Processor:

<FORM METHOD=post ACTION="http://webcom.com/~webcom/cgi-bin/form">

• WebCom Glimpse Indexing service:

<FORM METHOD=post ACTION="http://webcom.com/~webcom/cgi-bin/glimpse">

The WebCom Forms Processor looks for two hidden fields, which contain your WebCom userid and the name of the form being processed. If these are missing, an error message informing you that it could not identify the form name and/or the form owner.

<INPUT TYPE=hidden NAME="form_name" VALUE="nameofyourform">
<INPUT TYPE=hidden NAME="userid" VALUE="youruserid">

The WebCom Forms Processor looks for the configuration file, in a directory called "form", located in your home directory (the same directory within which your "www" directory is stored). The proper directory structure is shown below:

/pub
   /youruserid
     /adm
     /form
     /logs
     /www

If the "form" directory is missing, or you have placed the configuration file in your "www" directory, the Forms Processor assumes you have not created a form configuration file and engages in its default behavior.

Typical mistakes are to create a form configuration file named "filename.cfg", and then create hidden fields where the value of "form_name" is "filename.cfg" or "filename.html". The correct value is "filename", with the ".cfg" portion omited. An example of this is shown below:

<INPUT TYPE=hidden NAME="form_name" VALUE="nameofyourform">

The WebCom Forms Processor then automatically appends ".cfg" to the value stored in the form_name parameter, and looks for a configuration file called "nameofyourform.cfg" in your "form" directory.

If "filename.cfg" is the value, the Forms Processor will look for "filename.cfg.cfg" in your "form" directory, and not finding it, engages in its default behavior.

If the WebCom Forms Processor does not find the "form" directory, or does not find a form configuration file it can match to the "form_name" parameter in the HTML file containing the form into which the data being processed was entered, it assumes you have not created a configuration file, and uses its default behavior: sending you the content of your form in an e-mail message, and returning the standard message "Your Form has been submitted. Thank You!" to the users screen.

One other problem which can cause confusion is improperly opening the Form. Netcruiser (the WWW browser supplied by Netcom) ignores this, but Netscape will redisplay the form when it is submitted, rather than calling the WebCom Forms Processor as the action of the following line instructs it to.

Wrong:

<FORM> (this causes Netscape to become confused, Netcruiser ignores it)
<FORM METHOD="POST" ACTION="http://webcom.com/~webcom/cgi-bin/form">

Right:

<FORM METHOD="POST" ACTION="http://webcom.com/~webcom/cgi-bin/form">