WebCom CUSTOMER SUPPORT

HELP FOR WEBCOM'S TOOLS & SERVICES
WebCom
Support


Control Panel Login

Tools & Services
   · Domain Names
   · Email
   · FTP
   · Page Creator
   · File Manager
   · Form Processor
   · Hit Counter
   · Glimpse Indexing
   · Password Protection
   · Site Activity Reports
   · WebCommerce

Getting Started

FAQs

Glossary

Contact Support


 

Forms Processor Parameters

Contents   Index of Parameters   Search the Forms Processor Docs   

f_delimiter

Specifies the character to use as the file delimiter. The file delimiter is the character that surrounds the values in a file generated with the $file parameter. As with most parameters, this one may be set within the form (using a hidden field) or within the form configuration file.

This parameter can be set in one of 2 ways:
  1. <INPUT TYPE=HIDDEN NAME=f_delimiter VALUE="character">
  2. $f_delimiter="character";

    • character - The literal character that you wish to use to surround field values submitted from a form. The default is the quote("). The default makes your file look like this:

      input_field_name="data from field"

      If you change it to an astrisk (*) it would look like this:

      input_field_name=*data from form*

    • NOTE:
      Form Processor configuration files:
      If you change the delimiter to something that is a reserved character in the Form Processor (a character that has a special meaning to the Form Processor, such as ';', '#', '$', '\', '@', and '%'), you must put a backslash (\) in front of it.

Example:

Example of inline form syntax:

<form method=POST action="/cgi-bin/form">
<input type=hidden name=userid value=webcom>
<input type=hidden name=form_name value=testform>

<input type=hidden name=f_delimiter value="*">

<!-- NOTE: if you use the quote (the default anyway) you must escape it into
it's hex equivelent (%22) -->

<input type=submit>
</form>

# changes the delimiter to * for the file parameter

$f_delimiter="\*";

$file="data/output.dat";




WebCom Home

phone: 1-800-GETVERIO
© Verio Inc. 1996-2007 ::: Acceptable Use Policy ::: Privacy