• fpp-v5.zip - Archive of our Form Processor Pro Download Package
• fpp/ - Main Form Processor Pro folder with all required files for proper work. You must upload this folder to your public folder (www) on your web server.
• sample-forms/ - Folder with examples of typical forms. Feel free to use and change them for your needs.
• fpp/ - Form Processor Pro configured to serve sample forms. You should upload this folder to your web server with other sample-forms folder content to see how sample forms work.
• attachments/ - It is temporary folder for user uploads and files that you would like to attach in emails.
• classes/ - Classes are core files of Form Processor Pro.
  
• install/ - Initial configuration script.
• lang/ - Contains language files (translations) of all available languages for error messages. You can change language in a moment by changing only 1 string in configuration file. Please refer to “Language Settings”.
• plugins/ - Plug-ins directory. Each plug-in refers to certain functionality of Form Processor Pro.
• tmp/  - Form Processor Pro use this folder to store temporary files that may be needed during form processing, like PDF, XLS generated files, for counting unique submissions etc.
• .htaccess - .htaccess file prevent unauthorized access to the folder contents from the web.
• captcha.img.php - Provides CAPTCHA anti-spam protection.
• config.php - One and only configuration file of Form Processor Pro and forms. It has simple structure where you should specify all your forms and their settings, as well as global settings.
• index.php - Main Form Processor Pro executable file. All forms' actions should refer to this file. Like: <form name="my_form" action="URL_To_This_File">
• manual/ - This folder holds the HTML manual. In order to read it you should open index.html file from this folder.

Adding your own language

To add your own language, you have to create a new language file in fpp/lang

To do that just copy the previous en.lang.php file and rename to ##.lang.php , where ## is a two letter country code, e.g. fr.lang.php for France.

Then you have to translate the right part of the php file to the language selected.

Syntax:

Example:

should be in French:

Example:

Changing the Language

You can choose your language with the “language” setting.

Example (config file):

Result:

• Field Validations - validation rules, responsible for validating user input (e.g.: email validation, ZIP code validation)
• Actions - actions that are done after form submission (e.g.: send an email, put data in a database, open a web page)
• Modifiers - modifiers pre-format user inputted data by certain modification rules (e.g.: capitalize first letters of second name, set all letters of a special field to lowercase)

Click on the correspondent group for more information and the features reference.

1. Check permissions for the required files and folders
2. Configure the Email Sending feature (set the correct SMTP server)
3. Configure the Database settings (if you intend to save form submissions to the database)
4. Change the password for this configuration script

The script stores all parameters in the config.php file. And you can simply edit this file yourself if you understand what are you are doing and know your SMTP and DB parameters.

Run the Initial Configuration Script and follow the instructions in order to perform the initial Form Processor Pro configuration. The Initial Configuration Script is located in the fpp/install folder.

E.g.: If you've uploaded the fpp folder to the www root folder of your www.yourdomain.com  server, you can access the Initial Configuration Script via www.yourdomain.com/fpp/install/index.php.

When you've completed the Initial Configuration Script wizard, you are ready to set up your first form.

1. Modifiers overview
2. Modifiers Reference
1. capitalize
2. count_characters
3. count_paragraphs
4. count_sentences
5. count_words
6. csv_shielding
   
7. date_format
8. default
9. floorval
   
10. indent
11. lower
12. nl2br
13. regex_replace
14. replace
15. roundval
    
16. spacify
17. string_format
18. strip
19. strip_tags
20. truncate
21. upper
22. wordwrap
3. Combining modifiers

Modifiers overview

Modifiers used to perform certain transformations with user input prior to inserting results into a template or generating output.

Variable modifiers can be applied to any variable in a template tag. To apply a modifier, specify the value followed by the | (pipe) and the modifier name. A modifier may accept additional parameters that affect its behaviour. These parameters follow the modifier name and are separated by colons (:) and surrounded by double-quotes.

Examples:

The first example makes the value of the title variable all uppercase. The second truncates the value to 40 characters and add (…) at the end of the string and the third makes the value of the title variable all lowercased.

Modifiers Reference

capitalize

This is used to capitalize the first letter of all words in a variable.

Example:

count_characters

This is used to count the number of characters in a variable.

Example:

count_paragraphs

This is used to count the number of paragraphs in a variable.

Example:

count_sentences

This is used to count the number of sentences in a variable.

Example:

count_words

This is used to count the number of words in a variable.

Example:

csv_shielding

This is used to shield double quotes when using CSV file.

Example:

date_format

Returns a string formatted according to the given format string. Use variable %TIMESTAMP to get a timestamp

Example:

You can also use characters from following tables to customize the "date_format" modifier.

default

This is used to set a default value for a variable. If the variable is empty, the given default value is printed instead. Default takes one argument.

Example:

floorval

Deletes decimal part of digit

Example:

indent

This indents a string at each line (the default is 4). As an optional parameter, you can specify the number of characters to indent. As an optional second parameter, you can specify the character to use to indent with. (Use "\t" for tabs.)

Example:

lower

This is used to change a variable to lowercase.

Example:

nl2br

All line breaks will be converted to <br> tags in the given variable. It's very useful to output text area fields

Example:

regex_replace

A regular expression search and replace on a variable. Use the syntax for preg_replace() from the PHP manual.

Example:

replace

A simple search and replace on a variable.

Example:

roundval

Rounds a digit

Example:

spacify

Spacify is a way to insert a space between every character of a variable. You can optionally pass a different character (or string) to insert.

Example:

string_format

This is a way to format strings, such as decimal numbers. Use the syntax for the sprintf PHP function for the formatting.

Example:

strip

This replaces all repeated spaces, new lines, and tabs with a single space, or with a supplied string

Example:

strip_tags

This strips out markup tags, basically anything between < and >.

Example:

truncate

This truncates a variable to a character length (default is 80). As an optional second parameter, you can specify a string of text to display at the end of the string if the variable was truncated. The characters in the string are included with the original truncation length. By default, truncate will attempt to cut off at a word boundary. If you want to cut off at the exact character length, pass the optional third parameter of true.

Example:

upper

This is used to change a variable to uppercase.

Example:

wordwrap

This wraps a string to a column width (default is 80). As an optional second parameter, you can specify a string of text to wrap the text to the next line (default is carriage return \n). By default, wordwrap will attempt to wrap at a word boundary. If you want to cut off at the exact character length, pass the optional third parameter of true.

Example:

Combining modifiers

You can apply any number of modifiers to a variable. They will be applied in the order they are combined, from left to right. They must be separated with a | (pipe) character.

Example:

All template variable tags are enclosed within delimiters. These delimiters are  {#  and   #}. All content outside of delimiters is displayed as static content, or just as written. When Form Processor Pro encounters tags in templates, it attempts to interpret them, and displays the appropriate values in their place. The first variable in {#  #} is usually the name of a field whose value should be displayed.

Examples:

Lets say you have a text field named "first_name" on your form:

And you need to show the value in a preview. In the preview page you should set: 

And after user submitted the form and filled the field "first_name" with John, he will see on the preview page: 

It is very simple!

1. Introduction
2. Initial Configuration Script
3. Editing Pages
4. Editing Templates
5. Editing config.php

Introduction

Here, we'll guide you through the process of upgrading your existing form from Form Processor Pro v4 to Form Processor Pro v5.

To upgrade any form with Form Processor Pro, you only need to do four easy things:

1. Point your form to FPP and give your form a name. You should point the ACTION attribute of your form to the fpp directory and give your form a unique name by inserting a HIDDEN field in the form's HTML just after FORM tag.
2. Handle with error messages. Put the <!-- FPP_ERROR --> tag in your form's page in the where you'd like to display error messages.
   
3. Create the required Email, HTML and/or Log templates. Use {# and #} brackets and hash signs to include any variable (field content) in the template. If you have a text field with name=email then you can use this variable in any template by putting it in brackets like this: {#email#}. This will be changed to the submitter's entered value after processing.
4. Edit simple config file with required configurations. Set actions to perform, validation rules etc. All available actions, validations and modifiers can be found in this manual.

In this example we have a domain: mydomain.com and Form Processor Pro installed in the “fpp” public folder under the www root. In other words, Form Processor Pro can be accessed through: http://www.mydomain.com/fpp/index.php

Initial Configuration Script

Run the Initial Configuration Script and follow the instructions in order to perform initial Form Processor Pro configuration. The Initial Configuration Script (index.php) is located in the fpp/install folder. 

E.g.: If you've uploaded the fpp folder to www root folder of your www.yourdomain.com  server, you can access the Initial Configuration Script via www.yourdomain.com/fpp/install/index.php URL.

Editing Pages

You need to add the <base href...> tag directly after the <head> tag in your form page.

This line will prevent trouble with images, css, and urls that may appear after page processing.

If your page has the URL "http://yoursite.com/path/page.html", you need to add to the page:

Second, you need to change <form action> path to lead to the index.php file of Form Processor Pro v5, instead of the previous <form action...>. The form code should look like this:

where ../fpp/index.php is the relative path from form the page to Form Processor Pro. It can also be an absolute path like this:

Put the <!-- FPP_ERROR --> into your page, to show any error resulting incorrect input, you may insert it anywhere you want the user to see the error on your form page.

If you have more than one form page, you need to repeat these actions for every page.

Then you need to name your form, as all configurations are stored in one configuration file, Form Processor Pro needs to differentiate one from another, therefore for this you need to add this line just after form tag <form action...>:

where 'form_name' will be name of your form. This line only needs to be added to the first page of your form.

If you used CAPTCHA in you forms, there should be lines like this in your form:

You should change the first line  ("<img src...>) to:

where ../fpp/captcha.img.php is the path from this web page to the captcha.img.php file in your fpp folder

The input field can remain unchanged, but write down the name of the input field where you want to check the CAPTCHA code, as you will later use it in the configuration file.

Editing Templates

In Form Processor Pro v5, you need to use delimiters {# and #} instead of [ and ], so you need to open your templates in any plain text editor and change all the '[' bracket(s) to the '{#' and the ']' bracket(s) to the '#}' . So, if your email template looked something like this:

Previous email template:

It must be changed to this:

Editing config.php

Now in order to correct your final configurations we have to teach FPP how we would like our form to be processed. To do so, we have to edit config.php located in the fpp directory.

You need to open config.php file located in the fpp folder in any plain text editor, and add this line to the end of the file:

Where "form_name" is the name you gave the form in the FORM section of your web page HTML code.

This code designates where the form description starts. You can use the information from form.cfg file, but it needs to be modified. All lines that begin with '_error_path=' should be deleted, as errors now show on the form where the incorrect values are input.

The first line under form name should be:

Where formpage.html is the first page of your form, the path can be relative from config.php file to the page, it can be the absolute path, or you can use the URL of the page:

Paste you code from form.cfg file into the config.php file under the form declaration line.  You will now have lines like this:

You need to change '_browser_out=', '_browser_out1=' and so on to 'page = ' without any numbers.

All '_send_email#=' should be changed to 'email = ' also '_out_file=' should be changed to 'log_file = '

For more information about actions refer to the Actions chapter.

All validators now should be written into the config.php file in form description. Here are most popular and most useful validators:

To require a field to be filled:

Please note that phrases in ( and ) brackets are only used in error messages, not of internal field names in the HTML. Thus,     your error messages can be intuitive, user-friendly, and you can even use languages other than English! You can write the validation rules as one field per line or all in one string and separate field names by commas.

Thus:

or

These two examples will have the same effect - required form fields: name, email and subject.

In order to require only properly formatted emails in the email field we will use the “email_fields” validation rule, like we did above:

To activate CAPTCHA in your form, add this line

where 'r_captcha' is the name of the field, where submitter should input the value from CAPTCHA

For more information about validation rules refer to the Field Validations chapter.

That's all! We have finished upgrading your existing form from FPP v4 to FPP v5!

1. Introduction
2. Creating the contact form with an HTML editor
3. Configuring the form
4. Configuring the Thank You page
5. Creating Email templates
6. Configuring config.php - Summarizing the configuration

Introduction

Here, we'll guide you through the process of creating and configuring your first form with Form Processor Pro. After learning this sample  process you'll be able to configure any form in just 5 minutes or less! To begin with, we'll create a simple contact form with the following in mind:

• We will use the form fields: Name, Phone, Email, Subject and Comment
• We will validate Email field for properly formatted email addresses
• The Name, Email and Subject fields are required
• We want to send form results to our email address
• We want to send an auto-responder confirmation email to the person submitting the form
• We will provide the user with error messages on the same page and highlight empty or an improperly formatted email field
• We would like to have a custom thank you page with a personalized greeting

Hmm, that's pretty much of the requirements for a simple form! However, you can create significantly complicated and sophisticated forms with Form Processor Pro, too. In this case, we just want to have a contact form to be processed the right way and accept only correctly formatted submissions, avoiding user typos and mistakes.

To create any form with Form Processor Pro you only need to do four easy things:

1. Point your form to FPP and give your form a name. You should point the ACTION attribute of your form to the fpp directory and give your form a unique name by inserting a HIDDEN field in the form's HTML just after the FORM tag.
2. Handle error messages. Put the <!-- FPP_ERROR --> tag in your form's page where you'd like to display error messages.
   
3. Create the required Email, HTML, and/or Log templates. Use {# and #} brackets and hash signs to include any variable (field content) in the template. If you have text field with name=email then you can use this variable in any template by putting it in brackets like this: {#email#}. This will be changed with user's entered value after processing.   Be sure to use both the brackets ({}) and the pound signs (#).
4. Edit the config file with required configurations. Set the actions to perform, the validation rules etc. All available actions, validations and modifiers can be found in this manual. Remember you use the same configuration file for all forms.

In order to continue with the following  steps you need to have Form Processor Pro installed on your web server and the initial configuration should be complete. Please refer to the Installation section of this manual.

In this example, we have a domain: mydomain.com and Form Processor Pro installed in the “fpp” public folder under the www root. In other words Form Processor Pro can be accessed through: http://www.mydomain.com/fpp/index.php

Creating the contact form with an HTML editor

We've used Dreamweaver to create the form and we've got the following form and auto-generated HTML code:

Configuring the form

We will put the <!-- FPP_ERROR --> tag in the form's HTML in the place where we'd like to display error messages. (See the changed code below.) Now we need to point the form to be processed with Form Processor Pro.

We do this by editing the FORM tag's ACTION attribute to refer to the URL where Form Processor Pro resides. You can use either relative or absolute paths. We need to set the METHOD attribute as POST as well. And finally, set ENCTYPE as MULTIPART/FORM-DATA.

Form tag before: 

Form tag after required corrections: 

If you use a relative path in the action parameter and do not use a "Base href" tag, every page after first page must have the action="index.php" parameter:

That's all for the FORM tag. Now we need to give the form a unique name. Let's name it “contact_form”. We can do this by inserting a HIDDEN field just after the FORM tag with the name “fpp_form” and value “contact_form”. This name is not the same "name" as the name= value in the FORM tag.  FPP uses the hidden field to relate to the form.

Like this:

If you have more than one form page, repeat this step for each times. It's not necessary to add hidden field to pages other than first.

Save the form as: contact.html

Configuring the Thank You page

Since we want a  custom Thank You page we need to create it before dealing with the email template and the config file.

So, on the Thank You page we want to put something like this:

In order to insert any variables dynamically, we need to use the {# and #} brackets. Inside these brackets, we need to put the appropriate variable name. The variable name is of the corresponding field in our form. In our case, we should use {#name#} and {#email#} accordingly. So, we will have the following changes in our HTML code for the Thank You Page:

Creating Email templates

Email templates are simply text files with specially formatted content. Generally, email has the following required fields (rows in template): To, From, Subject and Message Body. However, other fields like BCC, Attachments etc. are also possible. Please refer to the Email Sending Action article for more information. An email template should look like this:

Email template:

In order to use variables (fields) we need to put them in curly brackets with pound signs (#), just like in the previous step. We want all form fields to be included in our email. So, the email template to be sent to us should look like this:

Save the Email template “to us” as: email.txt

We create the email template for the auto generated email to the form's submitter the same way:

Save the Email template “to client” as: autoresponder.txt

Configuring config.php - Summarizing the configuration

We have configured our form, thank you page and prepared the required email templates. Now in order to make the final configurations we have to teach FPP how we would like our form to be processed. To do so, we have to edit config.php located in the Form Processor Pro installation.

File placement on the web server

We modify/create config.php, we should place our created files to the web server, as we will use paths to these files in our config.php file. So, we place contact.html and thank-you.html in the web server's www public folder. Both email template files (email.txt and autoresponder.txt) we place in separate folder under www.

• www - public folder of mydomain.com
• fpp - folder with the installation of Form Processor Pro
• attachments
• classes
• install
• lang
• plugins
• tmp
• .htaccess
• captcha.img.php
• config.php (configuration file)
• fpp-test.php
• index.php
• style.css
• ..
• contact - folder with email templates
• .htaccess - to protect this folder from outside browsing, see tip-suggestion below
• email.txt
• autoresponder.txt
• contact.html  (our contact form)
• thank-you.html (our thank you page)
• .. - and other web site pages

In our case:

FPP can be accessed through: http://www.mydomain.com/fpp/index.php

Contact form can be accessed through: http://www.mydomain.com/contact.html

Tip: In order to protect your email template files from undesirable browsing through HTTP, we suggest you to place them in a separate folder and protect this folder from browsing. You can use an .htaccess file for this purpose on any Unix/Linux compatible host. Just add/create this file (.htaccess) in the folder with email templates with the following content (you can also copy the .htaccess file from “tmp” or “attachments” folder in the fpp folder):

You will protect yourself from email harvesting bots by doing this.

On Windows based hosts, you can do this by setting the corresponding permissions for this folder.

Adding a new form to the config.php file

Now we have all the required files in place and we can edit our config.php file

First, we have to declare a new form in our configuration file. We do this by adding a form name in [ ] brackets as a new line at the end of config.php file or just after global settings section. The form's name is the value used for previously added hidden files. In our case it's “contact_form”.

In our case we have:

After the form's declaration (form name in brackets) we can put any form settings we like.

Ok, now we have to declare all the pages that will be used during Form Processor Pro processing in a particular process order. We use the “page” setting for this purpose and set full or relative paths to these pages (relative to the fpp). If we would like to show a Thank You page just after the successful submission of our one-page contact form, we have to put it as second one.

Just like this:

Setting up validations

In order to set Full Name, Email and Subject fields as required, we need to use the “required_fields” validation rule and put all required field names here. Thus:

required_fields = name (Full Name), email (Contact Email), subject (Subject)

Please note that phrases in the ( and ) brackets (parentheses) are just used in error messages,not as internal field names in HTML. Thus your error messages can be intuitive, user-friendly, and you can even use language other than English! As we have already mentioned you can put validation rules as one field per line or write all of them  in one string and separate field names with commas.

Thus:

or

will have the same effect - required form fields: name, email and subject.

In order to require only properly formatted emails in the email field, we will use the “email_fields” validation rule, the same way as above:

As you can see you can have more than one validation per field, - any amount, actually, within reason, of course.

For more information on possible validation rules refer to the Field Validations chapter.

Setting up email sending

We would like to send two emails: one to us with form results and another as an auto responder to the person who submitted the form. We have already created these templates and we use them here with “email” action.

Like this:

For more information on possible actions refer to the Actions chapter.

That's all the configurations needed for the config.php file according to our initial requirements for this Contact Form.

That's all! We have finished configuring our first form!

1. Read Package Contents for a better understanding of further chapters in this manual.
2. Install the package according to Installation instructions.
3. Prepare your installation using configuration script and Initial configuration instructions.
4. Follow the steps in “Setting-up My First Form” chapter and configure your first form in order to understand the process of form configuration.
5. After succeeding these steps you'll be able to configure any form with FPP v5 just in 5 minutes or even less!

1. Overview
2. Field Validations Reference
1. allowed_values
2. australian_phone_fields
3. belgium_postcode_fields
4. canadian_provincial_fields
5. canadian_zip_fields
6. char_limit
7. char_min_limit
8. conditional_required_fields
9. credit_card_fields
10. date_fields
11. date_fields_delay
12. disallowed_characters
13. domain_fields
14. dutch_postcode_fields
15. email_fields
16. euro_serial_number
17. field_captions
18. field_list_exclude
19. file_filter_fields
20. float_fields
21. four_digit_year_fields
22. france_postcode_fields
23. french_phone_fields
24. german_postcode_fields
25. icd9_code_fields
26. image_file_fields
27. int_fields
28. ip_fields
29. ipv6_fields
30. is_fields_set
31. isbn_fields
32. italian_codice_fiscale_fields
33. italian_postcode_fields
34. mac_address_fields
35. month_fields
36. monthday_fields
37. msoffice_file_fields
38. netherlands_postcode_fields
39. percentage_fields
40. required_fields
41. required_empty_fields
42. roman_num_fields
43. same_fields
44. set_value
45. spanish_postcode_fields
46. ssn_fields
47. swedish_phone_fields
48. swedish_zip_fields
49. time_fields
50. uk_bsc_fields
51. uk_driver_license_fields
52. uk_nin_fields
53. uk_postcode_fields
54. url_fields
55. us_phone_fields
56. us_state_fields
57. vat_num_fields
58. vin_fields
59. weekday_fields
60. word_fields
61. word_limit
62. year_fields
63. zip_fields
64. zip_files_fields
3. File extensions allowed for upload

Overview

Form Processor Pro allows you to control, check, and verify user input data by using a number of bundled validating functions. It means you may set restrictions or requirements for any field on your form. For example, if you have some text field, named “your_email” and you want to be sure that all users provide you correct email address and nothing else; you should add the following line to your form configuration:

By doing this, you are forcing form users to provide you with a correct email address in the field named “your_email”

Detailed syntax of the major form validator configurations:

Where:

validator_name - is the name of the Form Processor Pro validator.

field_name1, field_name2 - are the names of the fields on your form. Names must be the the exact name of the HTML element.

Also, you may use special “field titles” for your fields, written in round brackets. They will be shown in error message, if the field contains any errors or mispellings, otherwise the field_name will be shown  if there is no field title specified.

Examples:

In example #1 we require form users to input a correct email address in field “email”. If it is not a valid email address the error message will be generating, like:

Field "Email address" is not correct email address

Example #2: we are checking the zip code on field “zip”. As you can see it is not necessary to use field titles.If the zip code is not valid,  the following message will be shown:

Field "zip" is not a correct zip code

Moreover, you can apply more than one field in a validation set. In example 3 above,  we set the fields name, zip, and email as required all in one validation line.

Field Validations Reference

allowed_values

Validates numbers validator (not less, not bigger or equal)

Syntax:

Example:

Result:

australian_phone_fields

Verifies Australian phone numbers. Matches all known formats including normal 10-digit landline numbers (valid area code mandatory) 13, 1300, 1800, 1900, 1902 plus mobile 10 and 11-digit formats.

belgium_postcode_fields

Validates postcodes for Belgium

canadian_provincial_fields

Validates provincial codes of Canada.

canadian_zip_fields

Verifies that Canadian postal code format is correct.

char_limit

Validates characters limit.

Syntax:

Example:

char_min_limit

Validates minimum characters limit.

Syntax:

Example:

conditional_required_fields

Checks if fields have been filled after checking user set condition.

Syntax:

condition_to_make_this_field_required can contains any expression using logical operators: = (for "equals"), != (for "not equals"), || (for "OR"), && (for "AND"). If you do not check the value of some field, Form Processor Pro will check if this field filled. Special parameters: contains and does_not_contain, which check if word or phrase is contained or not in some variable.

Example:

First line: if first_name is not empty, last_name will be required to be filled

Second line: if first_name and email are not empty, last_name will be required to be filled

Third line: if firs_tname has the value 'firstname' and email contains gmail.com, last_name will be required to be filled.

credit_card_fields

Verifies major credit card numbers, including: Visa, MasterCard, Diners Club, Carte Blanche, Discover and American Express.

IMPORTANT: It does not do REAL credit card validation; it only checks that the data input could be a credit card number.

date_fields

Validates date fields

date_fields_delay

Checks if date filled to the field isn't sooner of user set delay.

Syntax:

Example:

For example you need user only input into the date field date that is week further from today.

Result:

User won't be able to input date that is sooner than week from the day user submits the form.

disallowed_characters

Checks the field input and ensures that it doesn't have any of the listed disallowed characters.

Syntax:

Example:

domain_fields

Validates domain names.

dutch_postcode_fields

Dutch zip code verification

email_fields

Validates an RFC 2822 email addresses

euro_serial_number

Validates euro banknote serial numbers.

Syntax:

field_captions

This is not actually validator, but it used to set names of the fields that are not validated (for example for using them in generated files)

Syntax:

Example:

field_list_exclude

This option purges field from fields list, for example if you don't want some field to be shown while using Predefined Variable: {#%FIELDS_LIST_HTML#}, or if you don't want to show this field in the generated files.

file_filter_fields

File type validation. Allow a user to enter only files with allowed extensions.

See "File extensions allowed for upload" for examples.

float_fields

Validates decimal numbers

four_digit_year_fields

Validates the number of the year. Only used on four digit format.

france_postcode_fields

Validates postcodes for France (including colonies)

french_phone_fields

Validates phone numbers in France.

german_postcode_fields

Validates German postal codes (PLZ or Postleitzahlen)

icd9_code_fields

ICD9 code validation.

image_file_fields

Validates image file names.

int_fields

Validates integer numbers.

ip_fields

Validates the format of IP Addresses.

ipv6_fields

Validates full and compressed IPv6 addresses as defined in RFC 2373.

is_fields_set

Checks if fields was set (for example you pass with GET method to the form)

syntax:

isbn_fields

Validates ISBN number.

italian_codice_fiscale_fields

Validates Italian fiscal code (codice fiscale).

italian_postcode_fields

Checks postcodes for Italy (including possible Vatican/Italy indications)

mac_address_fields

Verifies a MAC address with hex values separated by a colon

month_fields

Month name (number) validation.

monthday_fields

Checks if the field value is between 1 and 31.

msoffice_file_fields

Microsoft Office filename validation.

netherlands_postcode_fields

Validates postcodes for the Netherlands.

percentage_fields

Validates percentage numbers.

required_fields

Checks if fields have been filled.

required_empty_fields

Checks if fields have not been filled.

roman_num_fields

Roman numerals validation.

same_fields

Checks to see if all listed fields have the same value.

Usage:

Example:

This example will validate fields email and email2 to have same values.

set_value

Used to set a value to the variable. For example if you want to have some predefine variable.

Usage:

Example:

Result:

{#company#} will show MyCompany, and {#state#} will show Alabama

spanish_postcode_fields

Validates Spanish postcodes

ssn_fields

U.S. social security numbers (SSN) validation

swedish_phone_fields

Validates Swedish phone numbers according to SIS standard

swedish_zip_fields

Validates Swedish zip codes (postnr) with or without space between groups. With leading s- or not

time_fields

Checks to see if values are correct timestamps.

uk_bsc_fields

Validates UK Bank Sort code

uk_driver_license_fields

Checks for UK Drivers License format

uk_nin_fields

UK National Insurance Number (NINo) validation

uk_postcode_fields

UK postcode validation

url_fields

Checks to see if the value is a correct full URL address.

us_phone_fields

Checks for US phone numbers with optional leading 1, an optional area code, and optional delimiters (hyphen, space, or period)

us_state_fields

Chekcs US state two character abbreviations

vat_num_fields

Validates VAT numbers

vin_fields

Checks Vehicle Identification Numbers (VINs)

weekday_fields

Weekday names (numbers) validation.

word_fields

Checks for single words

word_limit

Validates if number of words not greater than stated.

Syntax:

Example:

year_fields

Validates the number of the year.

zip_fields

US (ZIP and ZIP+4) validation

zip_files_fields

Checks for zip archive files extents

File extensions allowed for upload

Set the allowed file extensions for user uploaded files in file_filter_fields.

Syntax:

Example:

In your form:

Config file:

Result:    

Only *.gif, *.bmp, *.png files are allowed for user upload.