Plugin Documentation

How it works?

From the dashboard/configuration area the process is as follows:

1. Insert data fields into the form
2. Insert a calculated field and define the calculation rule on it to store the calculated value
3. Configure the general form processing, email and PayPal settings if needed
4. Publish the form from a post or page (go to edit posts or pages).

From the end user (visitor) point of view, the process is as follows:

1. The user fills the data fields
2. The calculated fields (if any) will automatically show the calculated value
3. If the form Processing is enabled:
   • If PayPal integration isn't enabled:
     1. The user clicks "submit" and you (the website owner or administrator) receive a notification email with the data posted by the user.
     2. The user receives an automatic "confirmation/thank you" email.
     3. The user is redirected to a "confirmation/thank you" page into your WordPress website
   • If PayPal integration is enabled:
     1. The user clicks "submit" and is automatically sent to PayPal for the payment
     2. In background (transparent to the user): The request is saved into the local database and mark as "un-paid"
     3. The user completes the payment at PayPal
     4. In background (transparent to the user): Upon completed the payment, you (the website owner or administrator) receive a notification email with the data posted by the user.
     5. In background (transparent to the user): The request is marked as "paid".
     6. The user receives an automatic "confirmation/thank you" email.
     7. The user returns to a "confirmation/thank you" page into your WordPress website

Installation

To install the WordPress plugin follow these steps:

1. Download the plugin to your computer.
2. Go to the plugins section in WordPress
3. If has been installed another version of the plugin, deactivate it, and then press the corresponding "Delete" button.
4. Press the "Add New" button at top of section.
5. Press the "Upload Plugin" button, and select the zipped file downloaded in the first step.
6. Finally, install and activate the plugin.

Inserting the CFF on Page

1. Configure the settings at the administration menu >> Settings >> Calculated Fields Form.
2. To insert a form into some pages or posts, uses the icon that will appear when editing contents:
   
   
   
   
3. After doing that, the tag [CP_CALCULATED_FIELDS id="1"] will be inserted into your content. The "id" is optional, if not specified the first form will be used. When you preview the content in the public website that tag will be replaced by the reservation form:
   
   
   
   Note: To assign a classes names to the forms, use the "class" attribute with the classes names separated by blank characters: [CP_CALCULATED_FIELDS id="1" class="class-a class-b class-c"]
   
   
4. The Claculated Fields Form includes multiple predefined designs.
   
   

Register the plugin

The "CFF" is completely functional even without be registered. But after registering the plugin, the updates are received directly into WordPress.

For registering the plugin follows the steps below:

1. Go to the settings page of the plugin through the menu option: "Settings/Calculated Fields Form"
2. Enter the email address used to purchase the plugin, in the attribute: "Enter the email address of buyer"
3. Press the "Register" button.

After registering the plugin the updates are notified in the "Updates" section of WordPress.

Managing Forms

After going to the WordPress administration menu >> Settings >> Calculated Fields Form you will see the list of forms like in the following image:

For each form you will see the following options:

• ID: Identification number of the form, useful when publishing an specific contact form.
• Form Name: Name to identify the form. Visible only from the admin area.
• Update: Updates the form name.
• Settings: For managing the form settings.
• Clone: Duplicate/clone a form.
• Messages: Printable list of messages (both paid and unpaid).
• Delete: Deletes the form and all its messages and settings.
• Shortcode: An alternative way for publishing the form.

After clicking the "Settings" button you will jump to a new page with the form builder a other configuration options as explained below.

The Form Builder

The Form Builder lets you to add/edit/remove fields into the form and also to specify the validation rules for your form (required fields, email fields, etc...).

SELECT column1 AS value, column2 AS text FROM tablename WHERE column3 > 5 ORDER BY column2 ASC LIMIT 5

SELECT ID as value, post_title as text FROM {wpdb.posts} WHERE post_author={user.id}

Settings area of the forms

For each form you will be able to edit the following settings:

Form Builder: Already explained in the previous sections (see above).

Displaying Form Summary in the Thanks Page

• Go to the thanks page
• Press the icon indicated in the next image, to insert a shortcode with format [CP_CALCULATED_FIELDS_RESULT]

The shortcode to insert in the thanks page allows a total control over the content to display with it.

In case to display all fields submitted with the form, is as simple as insert the shortcode: [CP_CALCULATED_FIELDS_RESULT]. But what to do if you want include in the thanks page only some of submitted fields, and not all?

The shortcode allows define the "fields" attribute, to select the fields names to include in the thanks page, separated by the comma symbol. For example, suppose the form has three fields: fieldname1, fieldname2, and fieldname3, but we want include only the fieldname1, and fieldname3, and exclude the fieldname2, in this case the shortcode would be:

[CP_CALCULATED_FIELDS_RESULT fields="fieldname1,fieldname3"]

But in some cases, we need more control over the content to display. By default, the shortcode is replaced by pairs of label-value for each field included in the thanks page. But what happen if you want display the label of fieldname1 in bold, or use a different label for the fieldname2, that the label used in the form?. In this case you should use the shortcode like a tag: [CP_CALCULATED_FIELDS_RESULT]...[/CP_CALCULATED_FIELDS_RESULT], and its content would be common HTML tags, with the field names using the same format that in the notification emails: <%fieldname#%>, to display only the label <%fieldname#_label%>, and to display only the value <%fieldname#_value%>. So, in this case the shortcode would be:

[CP_CALCULATED_FIELDS_RESULT]
<p><%fieldname1_label%>:<%fieldname1_value%></p>
<p>New Label: <%fieldname2_value%></p>
<p><%fieldname3%></p>
[/CP_CALCULATED_FIELDS_RESULT]

To get the complete list of tags to include in the thank you page, read the "SPECIAL TAGS IN THE NOTIFICATION EMAILS" section .

Associate a same thank you page with multiple forms

The forms' structures can be very different, and an unique shortcode wouldn't be sufficient to represent all forms. An option would be insert a different summary shortcode for each form, defining the attribute: "formid" indicating the form's id, in each of shortcodes, in whose case the plugin will replace only the shortcode corresponding to the form that has been submitted:

[CP_CALCULATED_FIELDS_RESULT fields="fieldname1,fieldname3" formid="1"]

[CP_CALCULATED_FIELDS_RESULT fields="fieldname8,fieldname9,fieldname14" formid="2"]

[CP_CALCULATED_FIELDS_RESULT formid="4"]

[CP_CALCULATED_FIELDS_RESULT formid="5"]
<p><%fieldname1_label%>:<%fieldname1_value%></p>
<p>New Label: <%fieldname2_value%></p>
<p><%fieldname3%></p>
[/CP_CALCULATED_FIELDS_RESULT]

Displaying the list of submissions

• To display the list of summaries insert the shortcode [CP_CALCULATED_FIELDS_RESULT_LIST]

This shortcode is similar to [CP_CALCULATED_FIELDS_RESULT]. With this shortcode it is possible to display all submitted fields or controlling the fields and format of the summary.

However the [CP_CALCULATED_FIELDS_RESULT_LIST] requires the formid attribute with the form's id. For example: [CP_CALCULATED_FIELDS_RESULT_LIST formid="1"]

Or at least a submission's id: [CP_CALCULATED_FIELDS_RESULT_LIST submission="123"]

There are other attributes supported by the [CP_CALCULATED_FIELDS_RESULT_LIST] shortcode, but these are optional:

• submission: the list of submissions ids separated by comma. [CP_CALCULATED_FIELDS_RESULT_LIST formid="1" submission="8,20,230"]
• from: a text with date format (yyyy-mm-dd) to display the list of submissions from a specific date. [CP_CALCULATED_FIELDS_RESULT_LIST formid="1" from="2018-04-09"]
• to: a text with date format (yyyy-mm-dd) to display the list of submissions until a specific date. [CP_CALCULATED_FIELDS_RESULT_LIST formid="1" to="2018-04-09"]
• order: used for ordering the submissions in ascending or descending order. The accepted values are: ASC and DESC. [CP_CALCULATED_FIELDS_RESULT_LIST formid="1" from="2018-01-01" to="2018-04-09" order="DESC"]
• limit: used to display a specific number of submissions. [CP_CALCULATED_FIELDS_RESULT_LIST formid="1" limit="10"]

For controlling the format of submissions' summaries it is possible to insert the shortcodes with a content, similar to:

[CP_CALCULATED_FIELDS_RESULT_LIST formid="1"]
<p><%fieldname1_label%>:<%fieldname1_value%></p>
<p>New Label: <%fieldname2_value%></p>
<p><%fieldname3%></p>
[/CP_CALCULATED_FIELDS_RESULT_LIST]

The complete list of tags to include in the shortcode is avalialbe in the "SPECIAL TAGS IN THE NOTIFICATION EMAILS" section .

Special tags in the notification emails and the thank you pages

There are special tags that can be used in the notification emails to display the forms information:

<%INFO%>, the tag <%INFO%> is replaced by the labels and values of fields that are submitted from the form.

To insert only specific fields, use the format <%fieldname#%>, for example, if you want include the fieldname1 and fieldname3 in the notification email, use the tags <%fieldname1%>, and <%fieldname3%>, the tag will be replace by the pair: label-value of field.

To insert only the field's label, use the format <%fieldname#_label%>, for example <%fieldname1_label%>

To insert only the shortlabel (that is used too in the CSV files), use the format <%fieldname#_shortlabel%>, for example <%fieldname1_shortlabel%>

To insert only the field's value, use the format <%fieldname#_value%>, for example <%fieldname3_value%>

To display all previous tags only if the fields have been filled by the users, you should use the attribute if_not_empty in the tags:

<%INFO if_not_empty%>
<%fieldname# if_not_empty%>
<%fieldname#_label if_not_empty%>
<%fieldname#_value if_not_empty%>

There are other special attributes to use in the tags. The values of the attributes are closed between the symbols {{...}}:

before: The attribute allows to define a symbol, or a HTML tag, to display before the field in the notification email <%fieldname# before={{<strong>}} after={{</strong>}}%>

after: The attribute allows to define a symbol, or a HTML tag, to display after the field in the notification email <%fieldname# after={{<br />}}%>

These attributes give a big control over the information included in the notification emails. For example, inserting a tag like:

<p><%fieldname1 if_not_empty%></p>

Inserts in the notification email, the pair of tags: <p></p>, if the value of the "fieldname1" field is empty. But if you inserts the previous tag with the attributes: before and after, like follow:

<%fieldname1 if_not_empty before={{<p>}} after={{</p>}} %>

The pair of tags <p></p> won't be inserted in the notification email, if the value of the fieldname1 field is empty.

separator: Allows to define a separator symbol to insert between the field's label, and its value. For example, if you insert the tag like: <%fieldname1 separator={{:}}%>, it would be replaced by field label : field value

There are some special tags to define dependencies in the notification emails: <%fieldname#_block%><%fieldname#_endblock%>

For example, to insert the fields: fieldname2 and fieldname3 in the email, only if the fieldname1 field was submitted, should be inserted the following tags in the email:

<%fieldname1_block%>
<%fieldname2%>
<%fieldname3%>
<%fieldname1_endblock%>

and <%fieldname#_nonblock%><%fieldname#_endnonblock%>

For example, to insert the fields: fieldname2 and fieldname3 in the email, only if the fieldname1 field was not submitted or it was submitted in blank, should be inserted the following tags in the email:

<%fieldname1_nonblock%>
<%fieldname2%>
<%fieldname3%>
<%fieldname1_endnonblock%>

Other attributes to include with the fields tags and the blocks tags:

if_value_is_greater_than includes the field (or block) if the field's value is greater than this attribute. For example: <%fieldname1 if_value_is_greater_than={{10}}%> the fieldname1 field would be included only if its value is greater than 10 (useful in case of number fields)

if_value_is_greater_than_or_equal_to includes the field (or block) if the field's value is greater than or equal to this attribute. For example: <%fieldname1 if_value_is_greater_than_or_equal_to={{10}}%> the fieldname1 field would be included only if its value is greater than or equal to 10 (useful in case of number fields)

if_value_is_less_than includes the field (or block) if the field's value is less than this attribute. For example: <%fieldname1 if_value_is_less_than={{10}}%> the fieldname1 field would be included only if its value is less than 10 (useful in case of number fields)

if_value_is_less_than_or_equal_to includes the field (or block) if the field's value is less than or equal to this attribute. For example: <%fieldname1 if_value_is_less_than_or_equal_to={{10}}%> the fieldname1 field would be included only if its value is less than or equal to 10 (useful in case of number fields)

if_value_is includes the field (or block) if the field's value is equal to this attribute. For example: <%fieldname1 if_value_is={{10}}%> the fieldname1 field would be included only if its value is equal to 10

if_value_is_not includes the field (or block) if the field's value is different to this attribute. For example: <%fieldname1 if_value_is_not={{10}}%> the fieldname1 field would be included only if its value is not 10

if_value_like includes the field (or block) if the field's value is included into this attribute. For example: <%fieldname1 if_value_like={{qwer}}%> the fieldname1 field would be included with value like qwerty (case insensitive). Recommended with text fields.

if_value_unlike includes the field (or block) if the field's value is not included into this attribute. For example: <%fieldname1 if_value_like={{qwer}}%> the fieldname1 field would be included with values do not include qwer (case insensitive). Recommended with text fields.

To include the URL to the uploaded file, if the file field is the fieldname1, the tag to insert in the email and thank you page would be: <%fieldname1_url%>, but if the fieldname1 supports multiple files, the corresponding tag would be: <%fieldname1_urls%>

To display the final price, after apply the discount if was defined, use the tag <%final_price%>

To display the coupon/discount applied, if was applied a discount, uses the tag <%coupon%>

To display only the coupon code, the discount text, use the tag <%couponcode%>

To display the payment option selected, in case that PayPal has been set as optional, use the tag <%payment_option%>

To display if the payment has been completed or not, use the tag <%payment_status%>

In the recurrent payments to display the id of the subscription, use the tag <%subscription_id%>

To include an unique number that identifies the submitted data into the system, uses the tag <%itemnumber%>. This number allows to identify easier the PayPal transference, and could be used as an order reference.

To include the form's id, uses the tag <%formid%>. Allows to identify the form that was submitted.

To include the ip address of the user, <%ipaddress%>

To include the submission date in the format: mm/dd/yyyy, <%submissiondate_mmddyyyy%>

To include the submission date in the format: dd/mm/yyyy, <%submissiondate_ddmmyyyy%>

To include the date in the format: mm/dd/yyyy, <%currentdate_mmddyyyy%>

To include the date in the format: dd/mm/yyyy, <%currentdate_ddmmyyyy%>

Create JavaScript variables to be used in the equations

- From GET, or POST parameters, SESSION variables, or COOKIES

The icon with the "X" symbol, that appears when editing the contents of pages or posts, inserts a shortcode in the content with the structure:

[CP_CALCULATED_FIELDS_VAR name="..."]

The ... symbol should be replaced by the parameter or variable name, and will be the same name of the javascript variable. For example: [CP_CALCULATED_FIELDS_VAR name="varname"]

To restrict the source of variable, define the attribute "from" in the shortcode with any of following values: get, post, session, or cookie. For example, to create the javascript variable: varname, only if exist a session variable with the same name, insert the shortcode: [CP_CALCULATED_FIELDS_VAR name="varname" from="session"]

The shortcode: [CP_CALCULATED_FIELDS_VAR] accepts two other attributes:

Definig default values

The "default_value" attribute allows to define the value used by default if there is not a parameter with the specified name, or session variable or cookie:

[CP_CALCULATED_FIELDS_VAR name="varname" default_value="mydefault"]

If there is not a parameter, or session variable, or cookie, with the name "varname", the plugin will create a global javascript variable with the name: "varname", and value: "mydefault".

Create direct variables

The attribute: "value", allows to create a javascript variable with the name defined as attribute, and the value in the attribute: "value".

[CP_CALCULATED_FIELDS_VAR name="varname" value="myvalue"]

After insert the shortcode to create the javascript variable, a valid equation would be: fieldname1*varname

Create a direct variable through the Forms Shortcode

There is another way to create global variables to be used in the equations, directly from the form's shortcode. All attributes in the shortcode, except the "id" that identifies the form, are converted in javascript variables with global scope, whose names correspond to the variable name, and their values, the attributes' values:

[CP_CALCULATED_FIELDS id="1" varname="varvalue"]

It is possible create multiple variables, defining multiple attributes.

The variables created through the form's shortcode have a particularity, for each global variable will be created another one with the structure: <variable name>_arr, for example: if the shortcode is:

[CP_CALCULATED_FIELDS id="1" varname="varvalue"]

The plugin will create two varaibles, the global variable: varname whose value would be varvalue, and the varname_arr variable, whose value is a hash with the varvalue as one of their items.

How to access to the value of the varname_arr?

Simply should be called the varname_arr variable, using as the index, the form_identifier constant: fieldname1*varname_arr[ form_identifier]

Pay attention to this way to access to the variables generated through the form shortcode. If there are multiple shortcodes inserted in the same page, and all of them define a same variable, accessing to the variable name through the scheme: <variable name>_arr[ form_identifier], each form will have its own value for the variable, because the global variable <variable name> will have only the latest value defined.

Add-Ons

The list of add-ons available in the plugin, appear in the "Add-ons area" of settings page of the plugin. For enabling the add-ons, simply should tick the corresponding checkboxes, and press the "Activate/Deactivate Addons" button.

Server Side Equations add-on

(Developer and Platinum versions of the plugin)

The Server Side Equations add-on allows to define equations in the server side to protect the business logic, and call them with AJAX from the public form.

The server side equations are defined from the settings page of the plugin, through the "Server Side Equations section".

The server side equations are shared by all forms in the website, reducing the development time.

Server Side Equations Structure

The server side equations are implemented with PHP programming language. The equations should be entered below the line of comment: INCLUDE YOUR CODE FROM HERE.

The equations should be defined into the GLOBAL array: "SERVER_SIDE_EQUATIONS", where the items' indexes are the names of the equations, and the items values are functions definitions with the code of the equations.

For example, assuming you want to implement an equation that calculate the square root of a number, a possible equation would be:

$GLOBALS['SERVER_SIDE_EQUATIONS']['square_root_equation'] = function($number){return sqrt($number);};

How the equations are called?

The add-on includes a new operations module with the operation: SERVER_SIDE for calling the server side equations using AJAX.

The "SERVER_SIDE" operation requires at least one parameter, the name of the server side equation (following with the previous example, the first parameter would be: 'square_root_equation') and the other parameters would be the parameters required by the server side equation.

SERVER_SIDE('square_root_equations',4)

the result would be 2

To get the square root of a field in the form, for example, the fieldname1, the equation would be:

SERVER_SIDE('square_root_equations',fieldname1)

Users Permissions add-on

(Developer and Platinum versions of the plugin)

The new add-on: "Users Permissions", allows restrict the access to the forms, and associate the submitted information to the submitter.

The options to restrict the access to the form are: Only for registered users, for registered users with specific roles, or allow the access to the form only to specific users.

With the "Users Permissions" add-on it is possible restrict the number of submissions to only one by user.

The add-on includes a new shortcode: [CP_CALCULATED_FIELDS_USER_SUBMISSIONS_LIST], to display the list of submissions belonging to an user. If the shortcode is inserted without attributes, the list of submissions will include those entries associated to the logged user. This shortcode accepts the attributes: id, for the user's id, and login, for the username (the id attribute has precedence over the login), in whose case the addon will list the submissions of the user selected, furthermore it is possible restrict the list to a specific form using the attribute: form="#", where # should be replaced by the form's id. The add-on allows to define the summary of the submitted data that will displayed in the list of submissions. Enter the summary's structure in the "Summary" attribute. In the summary can be use all the special tags, available for the notification emails, and the thank you pages.

The add-on allows to assign permissions for "edit" or "delete" the entries. Actually, the submissions are not deleted, or its data modified from these actions, the real control over the data is only for the website's administrator. In the first case, the submission will be disabled, and will be hidden from the list of user's submissions, but the submission is always accessed by the website administrator through the messages section, and if the data are edited, the original entry will be disabled, and a new entry is generated and associated to the user.

There are other features included by this add-on, the "Messages" section is modified to include in the list of submissions the name of the submitter, furthermore, includes a new input field for filtering the events by users.

Users Registration Form add-on

(Developer and Platinum versions of the plugin)

The new add-on: "User Registration Form", allows allows register new users through a form created with the Calculated Fields Form plugin.

The add ons allows even create the users' metadata required by other plugins.

Add-on settings

Enabled: Allows to enable/disable the users registration through the form.

Notification: Send a notification email to the new user, the website's administrator, both, or to none of them.

User email field(required): name of field in the form for the user's email.

User login field(required): name of field in the form for the user's login.

User password field: name of field in the form for the user's password. If there is not a field for password it is generated dynamically.

User nicename field: name of field in the form for the user's nicename.

Display name field: name of field in the form for the user's display name.

User url field: name of field in the form for the URL to the user's webpage.

User role: select the role to apply the new users.

User metadata section. Allows to add pairs of input boxes for entering the metadata name, and the field's name corresponding to the user's metadata.

Login required: Error message to display if the login is empty.

Login exists: Error message to display if there is an user with the same login.

Login too long: Error message to display if the login is longer than 60 characters.

Email required: Error message to display if the email is empty.

Email invalid: Error message to display if the value entered by the user has no valid email format.

Email exists: Error message to display if there is an user with the same email.

Nicename too long: Error message to display if the nicename is longer than 50 characters.

Upload add-on

(Platinum version of the plugin)

The "Upload Files" add-on allows to add the uploaded files through the forms to the Media Library, and access to them from the pages and posts of website.

Furthermore, it allows to include the support of new mime types, than files format supported by default by WordPress.

To add the uploaded files to the "Media Library" ticks the checkbox: "Add the uploaded files to the media library".

WordPress supports some specific mime types, for supporting new mime types, you simply should enter the files' extensions separated by comma.

Signature add-on

(Platinum version of the plugin)

The add-on converts the form fields selected in "Signature" fields, allowing the users to sign with the mouse or directly in the touchscreens.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-Signature", and press the "Update" button.

From the form's settings, selects the fields to convert in Signature fields. It is possible convert multiple fields in the form in signature fields.

Signature settings:

Color: the color code for signatures. For example: #000000

Line thickness: an integer number defining the line thickness of the signature.

Show guideline: checkbox to include or not a guideline in the signature fields.

Guideline color: the color code for guideline. For example: #000000

iCal add-on

(Platinum version of the plugin)

With the iCal addon the users will receive an iCal file as part of the confirmation email after the form submission. The iCal file allows to be imported into most popular calendars like Outlook and Google Calendar.

To activate the new iCal attachment add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF - iCal Export Attached", and press the "Activate/Deactivate addons" button.

With the add-on activated go to the form settings page and at the bottom of that page you can configure the iCal file that will be attached into the emails. You will need to specify the ID of the field that contains the date and you can modify the iCal content and time conversion settings if needed.

In the settings area the following information is needed to activate and setup the addon:

• ID of the field that contains the date: ID of the field that contains the date, must be a date field. Example: fieldname1. If empty the iCal won't be generated.
• iCal entry summary: Summary of the iCal event. You can get the field IDs/tags from the form builder to customize this field with the submitted data.
• iCal entry description: Description of the iCal event. You can get the field IDs/tags from the form builder to customize this field with the submitted data.
• iCal timezone difference vs server time: If you see differences in the selected and imported dates in the calendar then use this field to adjust that difference.
• Observe daylight saving time?: Indicates if the daylight saving time will be taken in account.
• Daylight saving time zone: If the daylight saving time will be used then indicate here the zone used as reference.

When enabled, after clicking the Calculated Fields Form submit button, an iCal file will be generated and attached to the emails.

WooCommerce add-on

(Developer and Platinum versions of the plugin)

The developer version of the plugin includes the WooCommerce add-on, to integrate the forms created by the "Calculated Fields Form" with the WooCommerce products. The add-on inserts an additional metabox in the WooCommerce products, with multiple settings fields:

• Enter the ID of the form: Allows select the form that will be associated to the product.
• Calculate the product price through the form: Allows calculate the price of the products through the form.
• Minimum price allowed: The minimum price applied to a product.
• Activate the summary: Allows customize the fields included in the cart page of WooCommerce.
• Summary title: Enter the summary title.
• Field for weight: Enter the form's field corresponding to the product's weight.
• Field for length: Enter the form's field corresponding to the product's length.
• Field for width: Enter the form's field corresponding to the product's width.
• Field for height: Enter the form's field corresponding to the product's height.
• Summary: Define the summary, are accepted all special tags supported by the notification emails and the thank you page.

Note: If you want calculate the price of products through the form, will be required that you select the field of the price in the attribute: "Request cost" in the form's settings.

Note 2: The fields for weight, length, width, and height, can be required to calculate the shipping cost by the "WooCommerce Table Rate Shipping" plugin.

MailPoet add-on

(Platinum version of the plugin)

The platinum version of the plugin includes the "MailPoet" add-on. It allows to add new subscribers to the MailPoet Mailing Lists with the information collected by the forms. The add-on adds a new metabox in the form's settings, to create the relationship between the form's fields and the data required by MailPoet:

• Firstname field: enter the name of the field in the form that collect the user's first name (this attribute is optional).
• Lastname field: enter the name of the field in the form that collect the user's last name (this attribute is optional).
• Email field: enter the name of the field in the form that collect the email (this attribute is required). It is possible to define multiple fields for emails to subscribe multiple users to MailPoet
• Mailing lists: this section includes an option for each mailing list active in MailPoet. It is possible pre-select the mailing list(s) to associate with the form, or allow the users select the mailing list by teirself. If the option to allow the users take the decision is selected, it is necessary insert a "HTML Content" field in the form, and enter in its content a DIV tag with an unique ID, and enter this ID into the "container" box, furthermore, it is possible configure the mailing lists as required fields in the form.

AffiliateWP add-on

(Platinum version of the plugin)

The platinum version of the plugin includes the "AffiliateWP" add-on. AffiliateWP is a WordPress plugin that gives the affiliate marketing tool needed to grow a business and make more money.

The add-on is enabled through the settings page of the plugin, ticking the "CFF - Affiliate WP" checkbox and pressing the "Activate/Deactivate addons" button.

The add-on allows to integrate the forms with the AffiliateWP plugin. It adds a new metabox in the form's settings, to activate the integration and define the description to use with referrals:

• Integrate the Affiliate WP with this form: Tick the checkbox to integrate the AffiliateWP plugin with the current form.
• Description: Enter the text to use as description of referrals in AffiliateWP.
  It is possible to use the special tags supported by the notification emails and the thank you pages with the referrals' descriptions.
• Context: Enter the text to use as the context for the referral.

Google Analytics add-on

(Platinum version of the plugin)

* Google Analytics is a third party service not related to our company.

The platinum version of the plugin includes the "Google Analytics" add-on to generate the usage reports in "Google Analytics" about the interactions of users with the form. The add-on adds a new metabox in the forms settings, to configure the events and exceptions that are sent to "Google Analytics" and when:

• Enter the property ID: property ID generated in Google Analytics.
• Send Fields section: enter the form's fields (fieldname#), and select the information to be sent to Google Analytics, and when.

Sends a hit of "Event" type for every onfocus event triggered by the field. The hits can include the field's label, and it is possible to decide if send only one hit by field, or for each "onfocus" event in the field. The hits are sent with the event's category: "form", and the event action: "focus", the label of the event includes the form's id, the field's name, and the field's label, if the corresponding option was ticked.

• Send Events section: tick the checkbox corresponding to each event to be reported to Google Analytics.

Sends a hit of "Event" type if the form is loaded, or for every action: "Next Page", "Previous Page", or "Submit". The hits are sent with the event's category: "form", and the events' actions: "load", "next page", "previous page", and "submit", respectively. Each event includes a label with the form's id, and in case of next and previous page events, the page number. The events "next page" and "previous page" allow to know the pages that are reached by the users, and identify problems in the form's structure. The "submit" event allows to know how many users complete the form, comparing the amount of "submit" events with the "load" events.

• Send Exceptions section: tick the checkbox corresponding to the exceptions to be reported to Google Analytics.

Sends a hit of "Exception" type in every failed submission by an incorrect "CAPTCHA" code. It allows to know if the "CAPTCHA" images are difficult to read, and modify its settings to solve the issue.

Google Places add-on

(Platinum version of the plugin)

The add-on integrates the input fields in the form with the Google Places API to autocomplete the address entered by the users. The user only need to start typing the address, and the add-on displays a list of addresses matching with the typed text.

* Google Places is a third party service not related to our company. Google Places may charge for their service.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-Google Places", and press the "Update" button...

...the plugin displays a new dialog for entering the Google API Key. The Key is not required, but it allows searching by more places than the use of the free API.

From the form's settings, selects the fields to associate with the Google Places API. It is possible apply the Google Places API to multiple fields in the form.

Furthermore it is possible restrict the search to one or multiple countries (maximum 5). The countries must be passed as as a two-character code, separated by comma.

reCAPTCHA add-on

(Developer and Platinum versions of the plugin)

The add-on allows to protect the forms using the Google reCAPTCHA instead of the captcha distributed with the plugin. reCAPTCHA is more visual and intuitive than the traditional captcha, with just a single click the users confirm they are not a robot.

reCAPTCHA (its official name is No CAPTCHA reCAPTCHA) as they define themselves:

reCAPTCHA is a free service that protects your website from spam and abuse. reCAPTCHA uses an advanced risk analysis engine and adaptive CAPTCHAs to keep automated software from engaging in abusive activities on your site. It does this while letting your valid users pass through with ease.

reCAPTCHA offers more than just spam protection. Every time our CAPTCHAs are solved, that human effort helps digitize text, annotate images, and build machine learning datasets. This in turn helps preserve books, improve maps, and solve hard AI problems.

To use reCAPTCHA in your forms, activate the add-on in the the settings page of the plugin, through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF - reCAPTCHA", and press the "Update" button.

* Google reCaptcha is a third party service not related to our company.

The activation of reCAPTCHA displays a new section for entering the site key, and the secret key, two keys provided by Google reCAPTCHA to protect the website, and validate the forms submissions respectively.

If the site key and secret key were generated for an invisible reCAPTCHA, it si possible to tick the "Is it a key for invisible reCAPTCHA?" checkbox in the add-on settings to insert reCAPTCHA as invisible.

SalesForce add-on

(Developer and Platinum versions of the plugin)

The add-on allows create new leads in the SalesForce account with the data submitted by the forms (https://www.salesforce.com).

* SalesForce is a third party service not related to our company. SalesForce may charge for their service.

To create new leads in SalesForce with the data submitted by a form, be sure that the SalesForce account has enabled the Web-to-lead option, and then go to the form's settings:

• Enter the OID (Organization ID)
• For debugging the lead creation, tick the "Enabling debug" option, and enter the email address where receive the information. For production, untick the debugging option.
• Press the "Add attribute" button, select the Lead attribute, and enter a fixed text, or the name of the field in the form (fieldname#)

Note: The Add-on includes the list of predefined attributes of Leads, but it is possible to enter custom attributes too.

WebHook add-on

(Developer and Platinum versions of the plugin)

The add-on allows posting the submitted information by the forms to WebHooks URLs. With the WebHook add-on it is possible integrate the forms created by the plugin with services like Zapier, Microsoft Flow, or IFTTT. Zapier, Microsoft Flow, and IFTTT connect services as important and popular as Zoho CRM, Dropbox, Mailchimp, Evernote, Google Drive, Facebook, Twitter, and more than 300 services(Zapier apps, Microsoft Flow, IFTTT)

Use this add-on is as simple as entering the WebHooks URLs, through the CFF-WebHook section in the forms settings, and tick the checkbox for sending to the webhook all fields submitted by the form, or define only some of fields. To associate multiple WebHooks to the form, simply press the "Add new url" button, and define the data for the new webhooks.

Note: Concerning to Zapier service, select Webhook as the Trigger app, and "Catch Hook" as the trigger for this app. For Microsoft Flow, select Request

* Zapier is a third party service not related to our company. Zapier may charge for their services.

* Microsoft Flow is a third party service not related to our company. Microsoft Flow may charge for their services.

* IFTTT is a third party service not related to our company. IFTTT may charge for their services.

WebMerge add-on

(Platinum version of the plugin)

The add-on sends the information collected by the form to the WebMerge service to generate a PDF file or Office document at runtime. Furthermore the generated document can be send to the user (https://www.webmerge.me/)

* WebMerge is a third party service not related to our company. Webmerge may charge for their service.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-WebMerge", and press the "Update" button...

After activate the WebMerge add on, the form settings will include a new section for entering the URL to the WebMerge document, and the correspondence between the variables in the document, and fields in the form.

Pressing the "Add a New Document" button it is possible to associate multiple documents to a same form, and pressing the "Add Field" button it is possible associate multiple variables and form fields to a document.

Each document in WebMerge has its own URL with the corresponding ID and Key code.

Using the WebMerge or WebHook add-on to integrate the form with Silverpop (Today IBM Watson Campaign Automation)

https://www.silverpop.com

1. In Silverpop (SP), build and publish a landing page form with all fields you want to use.

   From the web form properties, find the block of code labeled "External form post"

   

2. If the form tag has a structure similar to:
   <form method="post" action="http://mycompany.mkt9999.com/subgroup/myform" pageId="12345678" siteId="123456" parentPageId="12345678">

   Enter as the WebMerge document the URL (or the WebHook URL in the case of WebHook add-on): http://mycompany.mkt9999.com/myform?pageId=12345678&siteId=123456&parentPageId=12345678

3. Copy the "name" attributes of every field in the form, including the "hide" fields, to create the correspondence between the fields in the Silverpop form, and the name of fields in the form created with our plugin.

   For example, in the tag:
   <input type="text" name="Last Name" id="control_COLUMN4" class="textInput defaultText" style="margin: 0 3px 5px 3px; height: 20px; width: 294px;">
   the field's name would be: Las Name

   

   

DropBox Integration add-on

(Platinum version of the plugin)

The "DropBox Integration" add-on allows to copy or move the uploaded files through the forms to a DropBox.

* DropBox is a third party service not related to our company.

Enter the Token Access to access the DropBox account.

To remove the copies of files from the WordPress website, tick the checkbox: "Delete the local copy of file".

Note: To copy the files to the DropBox account is required create a DropBox App, and generate a token access.

ip2location add-on

(Platinum version of the plugin)

The add on integrates the Calculated Fields Form with the ip2location databases to identify additional information of users based on their IP, as: Country, City Name, Coordinates, Weather Station, Time Zone, ZIP Code, etc...

* ip2location is a third party service not related to our company. ip2location may charge for their databases.

Note: Requires PHP 5.3 and over.

Uplods the ip2location database's files to the correct location in the webserver (/wp-content/uploads/), and then, enters the files' names in the add on settings

Tick the checkboxes of the information you want get of users.

If has been selected the option to include the users information in the notification emails, and the add-on is enabled, the notification email will include all extracted data.

MailChimp add-on

(Platinum version of the plugin)

The add-on creates new members in the MailChimp service with the information collected by the forms in the website: www.mailchimp.com.

MailChimp is an online email marketing solution to manage subscribers, send emails, and track results.

* MailChimp is a third party service not related to our company. MailChimp may charge for their service.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-MailChimp", and press the "Update" button...

After activate the MailChimp add-on, the form settings will include a new section to create the correspondence between the signup form associated to a list in MailChimp, and the form fields in the form created with the "Calculated Fields Form" plugin.

1. Enter the API Key.
2. Press the "Get Lists" button. The action generates a list with all "Lists" associated to the MailChimp account.
3. Select the list and press the "Get Fields and Groups" button. The action displays multiple input fields, for connecting the fields in the form with the fields in the signup form of to the list, and the interests groups defined in MailChimp, that are displayed in the public form too to be selected by the users.

Emma add-on

(Platinum version of the plugin)

The add-on adds new members to the Emma's digital marketing platform with the information collected by the forms in the website.

* Emma is a third party service not related to our company. Emma may charge for their service.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-Emma", and press the "Update" button...

After activate the Emma add-on, would be available a new section for entering the "Account ID", "Public API Key", and "Private API Key" associated to the Emma account.

The Emma add-on includes a new section in the form's settings to create the relationship between the Emma fields and form's fields (press the "Get Fields" button to get the complete fields list), and select the Emma groups where to add the new members (press the "Get Groups" button to get the complete list of groups).

Twilio add-on

(Platinum version of the plugin)

The add-on integrates the forms with the Twilio service for sending notification messages (SMS) after submit the forms.

* Twilio is a third party service not related to our company. Twilio may charge for their service.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-Twilio", and press the "Activate/Deactivate addons" button...

After activate the Twilio add-on, would be available a new section section in the form's settings for entering the required data.

The add-on settings are:

Twilio enabled: for enabling/disabling the integration with the form.

Account SID: enter the Account SID provided by Twilio.

Authentication Token: enter the Authentication Token provided by Twilio.

From Phone Number: enter the phone number used as the "Origin" of SMS (enter a valid phone number including the country code).

To Phone Number: enter the phone numbers (separated by comma symbols) where to send the SMS (enter a valid phone number including the country code).

Message: enter SMS content (it is possible to use the same special tags than in the notification emails).

For sending a SMS to the phone number entered through the form

To Phone fields: enter the names of phone fields inserted in the form (fieldname#, separated by comma symbols).

Message: enter SMS content (it is possible to use the same special tags than in the notification emails).

PayPal Pro add-on

(Platinum version of the plugin)

With Payment Form for PayPal Pro you can insert a form into a WordPress website and use it to process credit card payments directly into your website without navigating to an external payment page.

You can check the differences betwen PayPal Pro and PayPal Standard at https://www.paypal.com/webapps/mpp/compare-business-products

For integrating PayPal Pro you must have a PayPal Pro account. In addition to that a SSL connection is also needed, the SSL connection isn't a technical requirement since the plugin can work without it but anyway it is strongly recommended for accepting credit cards into your website, otherwise the transactions won't be secure.

In the settings area the following information is needed to activate and link the PayPal Pro account to the form:

• Enable PayPal Pro: Select "Yes" to enable PayPal Pro.
• PayPal Pro - API UserName: The API Username provided by PayPal into your account.
• PayPal Pro - API Password: The API Password provided by PayPal into your account.
• PayPal Pro - API Signature: The API Signature provided by PayPal into your account.
• PayPal Pro - Currency: The currency for the payments, a valid PayPal currency code, example: USD, CAD, AUD, GBP, ...
• Paypal Mode: Select "Sandbox" for testing purposes and "Production" for charging real payments.

When enabled, the form on the public website will display an additional set of fields to request the data needed to process the payment, like for example the billing address, credit card details. This info is only for the payment processing, as mentioned it won't be stored into the website for security reasons.

After the submission Once the payment is processed and the posted data (excluding the credit card related information) is saved into the WordPress database.

Authorize.Net Server Integration Method (www.authorize.net) add-on

(Platinum version of the plugin)

The Authorize.net Server Server Integration Method (Authorize.net SIM) is a hosted payment processing solution that handles all of the steps in processing a transaction, including:

• Collecting customer payment information through a secure, hosted form
• Generating a receipt to the customer
• Securely transmitting to the payment processing networks for settlement
• Funding of proceeds to the merchant's bank account
• Securely storing cardholder information

Authorize.net SIM is an ideal integration solution because merchants are not required to collect, transmit, or store sensitive cardholder information to process transactions. Additionally, Authorize.net SIM does not require merchants to purchase and install a SSL or TLS digital certificate, reducing the complexity of securely handling and storing cardholder information, simplifying compliance with the Payment Card Industry (PCI) Data Security Standard. For more information go to www.authorize.net

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-Authorize.net Server Integration Method", and press the "Activate/Deactivate addons" button

In the settings area the following information is needed to activate and link the Authorize.net Server Integration Method account to the form:

Enable Authorize.net SIM?: Select "Yes" to enable the Authorize.net Server Integration Method payment.

Mode: Change the mode between "test" for testing purposes and "production" for accepting real payments.

API Username: Change this value with API Username received from Authorize.net.

API Key: Change this value with API Key received from Authorize.net.

Receipt URL: User will return here after a successfull payment. Important!: You must also configure the receipt link URL in the Merchant Interface.

Cancel URL: User will return here if payment fails.

In addition to the above required setting fields there are other fields to link the form fields to the Authorize.net payment form, like for example the client name, address, phone, email, ... These fields are optional. To link the fields you can indicate the ID of the field on the form that contains the related info. Sample values: fieldname1, fieldname2, ..

When enabled, the customer will be redirected to the Authorize.net Server Integration Method payment form after the submision. The process will be similar to the way PayPal Standard works.

Stripe (www.stripe.com) add-on

The Stripe Payments addon provides a way to accept all major cards from customers around the world on web. This addon requires SSL on your website to be able to carry the transaction in a secure way. Credit card data is entered directly in the website without navigating to an external page.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-Stripe Payment Integration", and press the "Activate/Deactivate add-ons" button...

In the settings area the following information is needed to activate and link the stripe account to the form:

• Enable Stripe?: Select "Yes" to enable the stripe Payments Integration.
• Stripe.com Publishable Key: Publishable Key you will find into your Stripe account.
• Stripe.com Secret Key: Secret Key you will find into your Stripe account.
• Payment frequency? Select "one-time payments" or recurrent (subscription) payments.
• Trial period length in days for subscription payments: If recurrent payments is selected put here the trial period length in days if any.
• Plan name for subscription payments: If recurrent payments is selected put here the plan name for subscription payments.

When enabled, after clicking the Calculated Fields Form submit button, a Stripe floating panel will be displayed to ask for the credit card data and process the transaction and after that the form submission will continue as usual keeping the customer all the time into your website.

Skrill (www.Skrill.com) add-on

(Platinum version of the plugin)

The Skrill Payments addon provides a secure interface for accepting payments through a secure page. You can accept cards, more than 20 local payment methods and over 80 direct bank transfer connections with a single integration. Form more information go to https://www.skrill.com/en/merchants/

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-Skrill Payment Integration", and press the "Activate/Deactivate addons" button.

In the settings area the following information is needed to activate and link the Skrill account to the form:

Enable Skrill Payments?: Select "Yes" to enable the Skrill Payments Integration.

Skrill Email?: Emai linked to the Skrill merchant account, this will be the account that will receive the payments.

Receipt URL: User will return here after a successfull payment.

Cancel URL: User will return here if payment fails.

Currency: Currency code for the received payment. example: USD, EUR, CAD, GBP ....

When enabled, the customer will be redirected to the Skrill hosted payment form payment form after the submision. The process will be similar to the way PayPal Standard works.

TargetPay (iDeal) add-on

(Platinum version of the plugin)

The TargetPay addon provides integration with iDeal, the most popular Dutch payment method. The integration is made via TargetPay: https://www.targetpay.com/info/ideal?setlang=en

With TargetPay you can set up iDEAL payments for your website easily. Acting as a "Payment Service Provider" it aggregates payments for a large number of webstores. The iDEAL platform combines the online banking systems of 10 of the largest Dutch banks (ABN AMRO, ASN Bank, Bunq, ING, Knab, Rabobank, RegioBank, SNS Bank, Triodos Bank and van Lanschot) into one payment method.

After the consumer selects the iDEAL payment method the consumer's bank is selected. The actual payment then takes place in the bank's trusted online banking environment for which security is guaranteed by the bank. Through iDEAL buyer and seller are guaranteed a transparent transaction without hidden fees or other unpleasant surprises.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-iDeal TargetPay", and press the "Activate/Deactivate Addons" button.

In the settings area the following information is needed to activate and link the iDeal-TargetPay account to the form:

Enable iDeal-TargetPay?: Select "Yes" to enable the iDeal-TargetPay payment option for the form.

RTLO Subaccount ID: Change this value with the account ID received from iDeal-TargetPay.

If payment fails return to this page: Return page if the payment fails or is cancelled before completing it.

Payments Mode: Change the mode between "test" for testing purposes and "production" for accepting real payments.

When enabled, the customer will be redirected to the iDeal-TargetPay payment form after the submision. The process will be similar to the way PayPal Standard works.

Mollie (iDeal) add-on

(Platinum version of the plugin)

The Mollie addon provides integration with iDeal, the most popular Dutch payment method. The integration is made via Mollie: www.mollie.com.

You're easily connected to iDEAL through Mollie without the dreaded technical and administrative hassle. The iDEAL platform combines the online banking systems of 10 of the largest Dutch banks (ABN AMRO, ASN Bank, Bunq, ING, Knab, Rabobank, RegioBank, SNS Bank, Triodos Bank and van Lanschot) into one payment method.

After the consumer selects the iDEAL payment method the consumer's bank is selected. The actual payment then takes place in the bank's trusted online banking environment for which security is guaranteed by the bank. Through iDEAL buyer and seller are guaranteed a transparent transaction without hidden fees or other unpleasant surprises.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-iDeal Mollie", and press the "Update" button...

In the settings area the following information is needed to activate and link the Mollie - iDeal account to the form:

Enable iDeal-Mollie?: Select "Yes" to enable the Mollie - iDeal addon.
Mollie API Key: The API Username provided by Mollie for your account, it may be the test key or the production key.
If payment fails return to this page: If the payment fails the customer is redirected to the page indicated in this field.

When enabled, the customer will be redirected to the Mollie - iDeal payment form after the submision. The process will be similar to the way PayPal Standard works.

RedSys / Servired / Sermepa add-on

(Platinum version of the plugin)

The RedSys / Servired / Sermepa addon provides a secure interface for accepting credit card payments through most banks in Spain (Sabadell, Banco Popular, BBVA, Santander, Bankia, Caixa, Bankinter, etc...). You can read more about RedSys at www.redsys.es.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-RedSys TPV", and press the "Update" button...

In the settings area the following information is needed to activate and link the RedSys account to the form:

Enable TPV: Select "Yes" to enable the RedSys TPV. If "Pay Later" or "PayPal" are also selected in this option, a radiobutton will appear in the form to select if the payment will be made with RedSys, with PayPal or if the form will be submitted without payment.
CÓDIGO COMERCIO: The API Username provided by RedSys or your bank.
CLAVE SECRETA: The API Password provided by RedSys or your bank.
Mode: Select "Sandbox" for testing purposes and "Production" for charging real payments.

When enabled, the customer will be redirected to the RedSys payment form after the submision. The process will be similar to the way PayPal Standard works.

SagePay add-on

(Platinum version of the plugin)

The SagePay addon provides a secure interface for accepting payments through SagePay. You can read more about SagePay at www.sagepay.co.uk.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-SagePay", and press the "Update" button...

In the settings area the following information is needed to activate and link the SagePay account to the form:

Enable SagePay?: Select "Yes" to enable the SagePay payment gateway.
Vendor ID: The Vendor ID provided by SagePay.
SagePay Encrypt Password: The SagePay Encrypt Password provided by PayTM.
Mode: Select "Sandbox" for testing purposes and "Production" for charging real payments.

When enabled, the customer will be redirected to the SagePay payment form after the submision. The process will be similar to the way PayPal Standard works.

Sage Payment add-on

(Platinum version of the plugin)

The SagePayments addon provides a secure interface for accepting payments through a secure SSL checkout system for both bankcard and virtual check transactions. All authorized and approved transactions will be delivered into your current bankcard and/or virtual check batches viewable within the Virtual Terminal for order processing and settlement. You can read more about Sage Payment Solutions at http://www.sage.com/us/sage-payment-solutions/accept-payments. The integration implemented in this addon is for Sage Payment Solutions >> Shopping ExpressPay

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", "CFF-SagePayments Payment Gateway", and press the "Update" button.

In the settings area the following information is needed to activate and link the Sage Payment Solutions >> Shopping ExpressPay account to the form:

Enable SagePayments?: Select "Yes" to enable the SagePayments TPV.

Merchant ID (M_id): Change this value with M_id received from SagePayments.

In addition to the mentioned two required setting field there are other fields to link the form fields to the Sage Payment Solutions payment form, like for example the client name, address, phone, email, tax and shipping cost. These fields are optionals and to link the fields you can indicate the ID of the field on the form that contains the related info. Sample values: fieldname1, fieldname2, ...

When enabled, the customer will be redirected to the Sage Payment Solutions payment form after the submision. The process will be similar to the way PayPal Standard works.

PayTM add-on

(Platinum version of the plugin)

The PayTM addon provides a secure interface for accepting payments through credit card, debir cards, net banking, wallet and EMI. With over 100mn Paytm users in India, your customers will love the option to pay with their trusted Paytm Wallet. You can read more about PayTM at paywithpaytm.com.

To activate the add-on, simply visit the plugin page through the menu option: "Settings/Calculated Fields Form", tick the checkbox: "CFF-PayTM", and press the "Update" button...

In the settings area the following information is needed to activate and link the PayTM account to the form:

Enable PayTM?: Select "Yes" to enable the PayTM payment gateway.
Merchant ID: The Merchant ID provided by PayTM.
Merchant Key: The Merchant Key provided by PayTM.
Website Name: The Website Name provided by PayTM.
Industry Type ID: The Industry Type ID provided by PayTM.
Mode: Select "Sandbox" for testing purposes and "Production" for charging real payments.

When enabled, the customer will be redirected to the PayTM payment form after the submision. The process will be similar to the way PayPal Standard works.

Equations Format for Calculated Fields

The equations allowed by the plugin "Calculated Fields Form" are really powerful tools.

Need more controls or operations?
Install the CP BLOCKS plugin:
- with buttons
- testimonial blocks
- additional features
...and more

It is possible create simple equations like follow:

With simple mathematical operations:

fieldname1+fieldname2

fieldname1*fieldname2

fieldname1/fieldname2

fieldname1-fieldname2

or mathematical equations with multiple fields and fields grouping included.

fieldname1*(fieldname2+fieldname3)

The equations may include a group of more specific operations

some of them available as buttons in the plugin's interface, the other operations should be typed manually in the equation's editor:

Pay special attention to the next two operations. The first of them, very extended its use in equations for calculations the cost of products and services, and the other one to obtain a date.

Sample valid equations:

To calculate the monthly payment in a lease calculator:

The fields implied are:

Load amount: fieldname1

Residual value: fieldname2

Interest rate %: fieldname3

Number of months: fieldname4

The corresponding equation for monthly payment is:

prec((fieldname1*fieldname3/1200*pow(1+fieldname3/1200,fieldname4)-fieldname2*fieldname3/1200)/(pow(1+fieldname3/1200,fieldname8)-1),2)

There is a huge number of equations that can't be recreated with simple mathematical operators, or the operations listed above.

Pay attention to the following sample:

In your form there are four fields: fieldname1, fieldname2, fieldname3 and the calculated field: fieldname4, but the value of fieldname4 is dependent of fieldname3 value, that is:

The value of fieldname4 will be: fieldname1+fieldname2, if the value of fieldname3 is greater than 100, or will be: fieldname1*fieldname2, if the value of fieldname3 is less than or equal to 100. Neither of previous operations, by itself, can calculate the value of fieldname4.

To solve complex cases like this, the "Calculated Fields Form" plugin allows entering javascript code directly in the equation editor, like the following sample:

(function(){

if(fieldname3 > 100) return fieldname1+fieldname2;

if(fieldname3 <= 100) return fieldname1*fieldname2;

})();

For complex equations where is required to define blocks of javascript code, you must use the following format:

(function(){

//Your code here

})();

and the return the value of that function will be the value assigned to the calculated field:

return fieldname1+fieldname2;

Pay attention, the plugin removes the changes of lines from the equations at runtime. So, if the equation is defined with the "function" format:

(function(){

//Your code here

})();

It is really important to include the semicolon symbols (;) at the end of the code lines, furthermore, if the equation is really complex, and you want to include comments for future references, should be used the format for multiple lines comments: /* comment here */, but never the format for single line of comments: // comment here

Logical Module

The logical module include the following functions:

Financial Module

The module includes a pack of functions to improve the implementation of financial equations. Distributed with the Developer or Platinum versions of the plugin.

The CALCULATEAMORTIZATION is the operation with most complexity in the "Calculated Fields Form" and requires its own section.

The CALCULATEAMORTIZATION operation returns a list of objects. For example:

CALCULATEAMORTIZATION(25000, 60, 5.25, new Date(2011,11,20) )

	Result:
		[
			{
				principle: 24634.725
				interest: 109.375
				payment: 474.65
				paymentToPrinciple: 365.275
				paymentToInterest: 109.375
				date: Tue Dec 20 2011 00:00:00 GMT+0100 (Romance Daylight Time)
			},
			{
				principle: 24267.851921874997
				interest: 217.151921875
				payment: 474.65
				paymentToPrinciple: 366.873078125
				paymentToInterest: 107.776921875
				date: Fri Jan 20 2012 00:00:00 GMT+0100 (Romance Daylight Time)
			},
			...
		]

• principle: how much remains to pay.
• interest: is the accumulated of interest paid until this date.
• payment: is the monthly payment (payment of interests and payment of principle).
• paymentToPrinciple: is the part of payment that is considered as payment of principle.
• paymentToInterest: is the part of payment that is considered as payment of interest.
• date: is the date of payment.

In the following example, we explain the use of the CALCULATEAMORTIZATION operation: the fieldname1 represents the principle amount, fieldname3 the number of months, and the fieldname2 the interest rate.

So, the value returned by CALCULATEAMORTIZATION(fieldname1,fieldname3,fieldname2) cannot by assigned directly to the calculated field, or will be displayed a text like: [object],[object],...... Therefore, we'll need to create a formatted string, with HTML tags, to display the CALCULATEAMORTIZATION results in an understandable format.

(function(){
var r = CALCULATEAMORTIZATION(fieldname1,fieldname3,fieldname2),
str = '';

if(r.length)
{
str = '<table cellpadding=" 10" >';
str += '<tr>';
str += '<td>Date</td>';
str += '<td>Interest</td>';
str += '<td>Payment</td>';
str += '<td>Payment to Interest</td>';
str += '<td>Payment to Principle</td>';
str += '<td>Principle</td>';
str += '</tr>';
for(var i = 0, h = r.length; i < h; i++)
{
str += '<tr>';
str += '<td>'+GETDATETIMESTRING( new Date(r[i]['date']), 'yyyy-mm-dd')+'</td>';
str += '<td>'+PREC(r[i]['interest'],2)+'</td>';
str += '<td>'+PREC(r[i]['payment'],2)+'</td>';
str += '<td>'+PREC(r[i]['paymentToInterest'],2)+'</td>';
str += '<td>'+PREC(r[i]['paymentToPrinciple'],2)+'</td>';
str += '<td>'+PREC(r[i]['principle'],2)+'</td>';
str += '</tr>';
}
str += '</table>';
}
jQuery('.comment_area .uh').html( str );
})()

The first step will be store the list of objects returned by the CALCULATEAMORTIZATION operation, in a local variable, and create another variable to store the amortization data, but with an HTML format:

var r = CALCULATEAMORTIZATION(fieldname1,fieldname3,fieldname2),
str = '';

The equation validates if the previous operation returns a value, because if the CALCULATEAMORTIZATION was called with wrong values can return an empty array:

if(r.length)
{
...
}

I've decided display the results of CALCULATEAMORTIZATION operation in a tabular format because is easier to understand. The first element in the result is the tag to open the table: <table>, and the row with the column names:

str = '<table cellpadding=" 10" >';
str += '<tr>';
str += '<td>Date</td>';
str += '<td>Interest</td>';
str += '<td>Payment</td>';
str += '<td>Payment to Interest</td>';
str += '<td>Payment to Principle</td>';
str += '<td>Principle</td>';
str += '</tr>';

Now, it is the moment to create each row of the table with the values of monthly amortization.

for(var i = 0, h = r.length; i < h; i++)
{
    str += '<tr>';
    str += '<td>'+GETDATETIMESTRING( new Date(r[i]['date']), 'yyyy-mm-dd')+'</td>';
    str += '<td>'+PREC(r[i]['interest'],2)+'</td>';
    str += '<td>'+PREC(r[i]['payment'],2)+'</td>';
    str += '<td>'+PREC(r[i]['paymentToInterest'],2)+'</td>';
    str += '<td>'+PREC(r[i]['paymentToPrinciple'],2)+'</td>';
    str += '<td>'+PREC(r[i]['principle'],2)+'</td>';
    str += '</tr>';
}

The previous code has its particularities. By default the dates returned by the CALCULATEAMORTIZATION operation have the complete format including hours and seconds, In this form the information about hours and seconds is not relevant, so, it is preferred to use a short date format: yyyy-mm-dd. The date string will be formatted with the GETDATETIMESTRING operation, included in the Date module of developers version of the plugin (the second parameter is the format to use):

str += '<td>'+GETDATETIMESTRING( new Date(r[i]['date']), 'yyyy-mm-dd')+'</td>';

Another particularity is the use of the PREC operation. By default the CALCULATEAMORTIZATION returns the numeric values with all its decimals digits, for example: 366.873078125, but for humans it is common to identify the money representation with two decimal digits. So, I've used the PREC operation with the number 2 as the second parameter.

str += '<td>'+PREC(r[i]['interest'],2)+'</td>';

After creating all table rows, it is time to close the table, and print the results:

str += '</table>';

If you display the result directly in the calculated field, you will see a weird text (or very hard to understand) because the input fields in HTML are not able to display tables, in this case I've preferred to show the result in an "Instruct Text" field. I've inserted an "Instruct Text" field in the form, this type of field uses the class name "comment_are", and includes an <span> tag with the class "uh". Then, using jQuery to select the correct field, I've inserted the formatted result of the CALCULATEAMORTIZATION in the <span> tag included in the "Instruct Text" field:

jQuery('.comment_area .uh').html( str );

The complete equation is:

(function(){
var r = CALCULATEAMORTIZATION(fieldname1,fieldname3,fieldname2),
str = '';

if(r.length)
{
str = '<table cellpadding=" 10" >';
str += '<tr>';
str += '<td>Date</td>';
str += '<td>Interest</td>';
str += '<td>Payment</td>';
str += '<td>Payment to Interest</td>';
str += '<td>Payment to Principle</td>';
str += '<td>Principle</td>';
str += '</tr>';
for(var i = 0, h = r.length; i < h; i++)
{
str += '<tr>';
str += '<td>'+GETDATETIMESTRING( new Date(r[i]['date']), 'yyyy-mm-dd')+'</td>';
str += '<td>'+PREC(r[i]['interest'],2)+'</td>';
str += '<td>'+PREC(r[i]['payment'],2)+'</td>';
str += '<td>'+PREC(r[i]['paymentToInterest'],2)+'</td>';
str += '<td>'+PREC(r[i]['paymentToPrinciple'],2)+'</td>';
str += '<td>'+PREC(r[i]['principle'],2)+'</td>';
str += '</tr>';
}
str += '</table>';
}
jQuery('.comment_area .uh').html( str );
})()

Date Time module

The Date Time module includes a group of operations to manage dates and times. Distributed with the Developer or Platinum versions of the plugin.

DISTANCE MODULE

The distance module integrates the Calculated Fields Form with the Google Maps (Distributed with the Developer or Platinum versions of the plugin):

Tip: To use your personal key for Google API, insert a shortcode for the variable: "google_api_key" in the webpage as: [CP_CALCULATED_FIELDS_VAR name="google_api_key" value="<your key>"]

The API Key can be defined directly in the form's shortcode, as follows: [CP_CALCULATED_FIELDS id="1" google_api_key="<your key>"]

SERVER SIDE MODULE

This operations module is distributed with the "Server Side Equations add-on" and includes the SERVER_SIDE operation for calling the server side equations with AJAX:

Troubleshoot Area & General Settings

The "Troubleshoot Area & General Settings" section, allows correct some possible issues, or conflicts with third party plugins, and define the general settings.

• Script load method: Changes the script load method if the form doesn't appear in the public website.
• Character encoding: Updates the charset, if you are getting problems displaying special/non-latin characters. After updated you need to edit the special characters again.
• Captcha image doesn't load: Tick the checkbox if the captcha code is not load, for calling the directly its script.
• Activate Javascript Cache: Allows caching the javascript files of the plugin.
• Activate Forms Cache: Stores the forms in cache to improve the website's performance.
• Modify the eMails Headers: If the notification emails are not send to the users, tries checking this checkbox, but if it is not sufficient, install and activate a SMTP plugin.
• Do not loading the forms with crawlers: The forms are not loaded when website is being indexed by search engine crawlers.
• Enter an unique field name: The name of the field that will be created to protect the forms against the spam bots. Adds a hidden text field to the forms to trap the spam bots.

Filters and Actions

The plugin calls the following list of filters and actions:

• cpcff_pre_form: Filters applied before generate the form, is passed as parameter an array with the forms attributes, and return the list of attributes, modified or not.
• cpcff_the_form: Filters applied after generate the form, is passed as parameter the HTML code of the form with the corresponding <LINK> and <SCRIPT> tags, and returns the HTML code to include in the webpage.
• cpcff_delete_form: Action called after delete a form, passing the form's id as parameter.
• cpcff_clone_form: Action called after cloning a form, passing two parameters, the original form's id, and the id of the new form.
• cpcff_export_addons: Filters applied when the form is exported, to export the add-ons settings too. Passes two parameters, an array with all the add-ons settings, and the id of the form that is being exported.
• cpcff_import_addons: Action called when a form is imported, to import the add-ons settings. Passes two parameters, an array with all the add-ons settings, and the id of the form that was imported.
• cpcff_valid_submission: Filters applied for checking if the form's submission is valid or not, returns a boolean.
• cpcff_redirect: Filters applied to decide if the website should be redirected to the thank you page after submissions, passes a boolean as parameter, and returns a boolean too.
• cpcff_csv_query: Allows modify the query of messages, passing the query as parameter, returns the new query.
• cpcff_get_option: Filters applied before returning a form option. Passes three parameters to the filter: The value of option, the name of option and the form's id, returns the new option's value.
• cpcff_messages_query: Allows modify the query of messages, passing the query as parameter, returns the new query.
• cpcff_process_data: Action called after be submitted the form, and processed the information in the server side.
• cpcff_payment_processed: Action called after receive the payment confirmation, passing as parameter the information collected by the form.
• cpcff_file_uploaded: Action called after upload a file through the form. It is passed as parameter the object returned by the wp_handle_upload function.
• cpcff_update_submission: Action called when a submission is updated, the submission ID is passed as parameter.
• cpcff_delete_submission: Action called when a submission is deleted, the submission ID is passed as parameter.
• cpcff_messages_filters: Additional filtering options, allows to add new fields for filtering the events in the messages screen.
• cpcff_messages_list_header: Action called to include new headers in the table of events in the messages screen.
• cpcff_message_row_data: Action called to add related data to the events in the messages screen, the row is passed as parameter.
• cpcff_script_after_validation: Action called in the generation of javascript code to validate the forms data before submission.
• cpcff_summary: Filters applied after generate the summary in the thank you pages. Passes the summary as parameter.

Tips and Tricks

<SCRIPT>
fbuilderjQuery(document).one('showHideDepEvent', function(){
	fbuilderjQuery
	.validator
	.addMethod(
		"zipcode",
		function(v,e)
		{
			return this.optional(e) || /^\d{5}([\-]?\d{4})?$/.test(v);
		}
	);
	fbuilderjQuery.validator.messages['zipcode'] = 'The  zipcode is invalid';
	fbuilderjQuery('[id*="fieldname1_"]').addClass('zipcode');
});
</SCRIPT>

define( 'DATABASE_HOST', '' );
define( 'DATABASE_USER', '' );
define( 'DATABASE_PASS', '' );
define( 'DATABASE_NAME', '' );
define( 'DATABASE_TABLE', '' );

$field1 = mysqli_escape_string( $db_link, $params[ 'fieldname%' ] );
$field2 = mysqli_escape_string( $db_link, $params[ 'fieldname%' ] );
$field3 = mysqli_escape_string( $db_link, $params[ 'fieldname%' ] );

$field1 = mysqli_escape_string( $db_link, $params[ 'fieldname1' ] );
$field2 = mysqli_escape_string( $db_link, $params[ 'fieldname2' ] );
$field3 = mysqli_escape_string( $db_link, $params[ 'fieldname3' ] );

mysqli_query( $db_link, "INSERT INTO `".DATABASE_TABLE."` (field1, field2, field3) VALUES ('$field1', '$field2', '$field3');" );

mysqli_query( $db_link, "INSERT INTO `".DATABASE_TABLE."` (firstname, lastname, email) VALUES ('$field1', '$field2', '$field3');" );

$field4 = mysqli_escape_string( $db_link, $params[ 'fieldname4' ] );

mysqli_query( $db_link, "INSERT INTO `".DATABASE_TABLE."` (firstname, lastname, email, year) VALUES ('$field1', '$field2', '$field3',$field4);" );

[CP_CALCULATED_FIELDS_RESULT]
<SCRIPT>
cpcff_default = { 1 : {},2 : {} };
cpcff_default[1][ 'fieldname3' ] = '<%fieldname1_value%>';
cpcff_default[1][ 'fieldname7' ] = '<%fieldname2_value%>';
cpcff_default[2][ 'fieldname2' ] = '<%fieldname1_value%>';
cpcff_default[2][ 'fieldname3' ] = '<%fieldname2_value%>';
</SCRIPT>
[/CP_CALCULATED_FIELDS_RESULT]

prefix="cp_cff_custom"
file="style.css"
title="Custom Template"
thumbnail="thumbnail.jpg"
description="This is my custom template"

.cp_cff_custom #fbuilder .fform h1{font-size:1.5em;}