[an error occurred while processing this directive]
Why is my Configuration File being ignored?

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".

Missing "form" Directory

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:

  /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.

Incorrect "form_name"

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.

[an error occurred while processing this directive]