CONFIGURATION
Form Configuration |
 |
 |
 |
 |
| Form Configuration There are several following peculiarities of web forms configuration to match Form Processor Pro requirements. First. Form Processor Pro 4.0 requires no variables in hidden fields unlike in previous versions. However, you may use any type of fields to pass to Form Processor Pro 4.0 information. In particular, you may override variables set in local form configuration form.cfg. This may be useful in forms, where the users next form page depends on choice it makes on previous pages. Example: Form has two radio buttons with one value to set: <input type="radio" name="_browser_out" value=" preview1.html" checked>Choice 1, <input type="radio" name="_browser_out" value=" preview2.html" >Choice 2. This fork makes Form Processor Pro 4.0 transit to user selected page by setting _browser_out to user’s choice. Second. A concern if you have several forms on your website. They need to be placed in different folders. As mentioned above, form fields, if their names set to variables names as in form.cfg, can override their values. So, different base paths, usually set in one directive, base_path, need to be set in the first page of the form: Example: <input type="hidden" name="base_path" value="path to the form folder”> See FPP Description /Local Form Configuration section for correct path settings in base_path. |
|
|
|
