General Form Settings

The Form Settings may be used to customize the action after submission, permissions, styling, and messages for an individual form. Configure your form's Settings by going into your form's → 'Settings'.

Basic Settings

When you first create a form, you will be asked to add a form name and description in the form builder. If you would like to make changes, you can edit it in the Settings → General Form Settings page.

• Form Title: Add a name to allow your users to get an overview of the form.
• Form Key: While this is automatically generated based on the form name that you first added, you can still change this if you want.
• Form Description: Add a description to provide information about the form such as instructions, notes, updates, and more.
• Show the form title: Select this checkbox if you would like the form title to be displayed with the form when published.
• Show the form description: Select this checkbox if you would like the form description to be displayed with the form when published.
• Embed button: Easily publish the form on a page/post.

On Submit

Choose what the user sees after an entry is submitted. Select one of the following: 'Show Message', 'Redirect to URL', or 'Show Page Content'.

Show Message

After an entry is submitted, a success message will appear. This message can be modified in the Messages section lower on the page. You can add any values from the submitted entry to your confirmation message, including conditional statements. You can also choose to include the blank form below your confirmation message. This is helpful if users will be submitting the form multiple times in a row.

If you would like to change the default 'On Submit' message, go to Formidable → Global Settings → Messages.

You can also choose whether to include the form with your message, with the option to 'Show the form with the confirmation message.'

Redirect to URL

Send users to another page or site after form submission. In the 'Redirect to URL' text field, insert the URL of the page where you would like to send the users.

Conditional statements can be used here as well, which will allow for conditional redirection based on a field selection in the form.

Redirect to a different site

To redirect to a different website, you can add this conditional statement directly in the 'Redirect to URL' text field.

http://[if 25 equals="Option 1"]site-a.com[/if 25][if 25 equals="Option 2"]site-b.com[/if 25][if 25 equals="Option 3"]site-c.com[/if 25]

Replace 25 with the ID of a field in your form and replace 'Option 1', 'Option 2', and 'Option 3' with the different options in this field.

If you are using separate values in this field, then you need to change [if 25 equals="Option 1"] to [if 25 show=value equals="Option 1"].

Redirect to a different page on the same site

If you want to redirect to a different page on the same site, you can add this conditional statement instead.

http://example.com/[if 25 equals="Option 1"]option-1/[/if 25][if 25 equals="Option 2"]option-2/[/if 25][if 25 equals="Option 3"]option-3/[/if 25]

Replace 25 with the ID of a field in your form and replace 'Option 1', 'Option 2', and 'Option 3' with the different options in this field. Also replace 'option-1', 'option-2', and 'option-3' with the pages where you want your users to be redirected.

If the user selects 'Option 1', then they will be redirected to the 'example.com/option-1' page in your site, if they select 'Option 2', they will be redirected to 'example.com/option-2', and if they select 'Option 3', then they will be redirected to 'example.com/option-3'.

Redirect using separate values

If you are working with long redirects on the same site, a simpler way of handling this is by using separate values. Note: This option will only work if your field options match exactly with your page slug.

http://example.com/[25 show="value"]

Replace 25 with the ID of the dropdown/checkbox/radio field in your form.

In your form builder, enable separate values and change the Saved Value for each option to the page slug that you want it to be redirected.

If the user selects 'Option 1', then they will be redirected to the 'example.com/option-1' page in your site. If they select 'Option 2', they will be redirected to 'example.com/option-2', and if they select 'Option 3', then they will be redirected to 'example.com/option-3'.

Need more advanced control of the form conditional redirect? See the code examples for the frm_redirect_url hook.

Show Page Content

Present a message from another page when an entry is submitted. If you have a page you would like to protect by requiring a form to be submitted before viewing, this is a good option. You can mark the page as Private, making it inaccessible to users, but the content from that page can still be used in the success message.

Note: If you choose to show another page's content on submit and the page has Javascript (e.g. tabs and accordions), don't enable AJAX submit. This will allow the Javascript on the other page to load properly.

Form confirmation page

To create a form confirmation page that contains the submitted values of the form, follow the steps below.

1. Select Show Message in your form settings. The On Submit box will automatically appear in the Messages section.
   
2. Piece together the message that you would like to show on the confirmation page. By clicking the three dots on the top right side of the message box, it will display the form's field IDs which you can use in the confirmation message. You can also add HTML and inline CSS to this message box to style your message.
   
3. Copy this message and paste it into the HTML text box of a WordPress page. This will be your confirmation page.
   
4. Return to your form settings and change the action from Show Message to Show Page Content. In the Select a Page dropdown, select the confirmation page that you created and click the Update button.
   
5. After submitting an entry to the form, the user will then be redirected to the confirmation page that was created.

Storing entries

You can choose if you would like to save entries from this form or not. All the entries will be saved automatically unless the Do not store entries submitted from this form is checked. Note: There is no way of retrieving entries that are not saved.

AJAX

Load and save form builder page with AJAX

This is recommended for long forms. Instead of a complete page refresh when you load or update a form, the form will be loaded and saved with Ajax. This will make the load time considerably faster for long forms.

Submit this form with Ajax

Allows the user to submit the form without a page refresh. Ajax refreshes only the form when the user hits Submit by exchanging data with the server and updating parts of a web page without reloading the whole page.

Validate this form with javascript

Required fields, phone format, email format, and number format can be checked instantly in your browser. After typing into a field the format will be checked, and any error messages for the field will be immediately added or removed without clicking the submit button.

Some types of validation are still run after submit, when communication is needed with the server. This includes unique fields, spam checks, and other PHP validation. Depending on your form, especially if you have any customizations to remove validation messages on certain fields, it may be better to keep javascript validation turned off.

Form Permissions

Limit form visibility and submission

Allows you to choose which user roles can see and submit the form. A logged-in user is someone who is logged in with a WordPress user account on your site before filling out the form. Note: Even if you don't publish your form, it may be accessible via the preview URL. If you do not want unauthorized users submitting your form, we recommend that you set the form visibility to prevent this.

Limit number of form entries

You may choose to limit number of form entries to one per logged-in user, IP address, or saved cookie.

Allow front-end editing of entries

This will allow certain users to edit form submissions. You may allow a particular user role to edit their own submissions or all form submissions. To learn more about editing responses, click here.

• On Update: If you allow front-end editing of entries, you may choose what the user sees after the form is updated.

Allow logged-in users to save drafts

Allows the logged-in user to save a partially completed form as a draft. A logged-in user is someone who is logged in with a WordPress user account on your site before filling out the form. When the user returns to the form, he/she can continue where they left off. Users can save their draft as many times as they would like, but once it is submitted, it cannot be reverted to a draft. Each user can only have one draft at a time.

If you have set your emails to trigger when a Draft is saved, only the first draft is saved.

Additionally, when this option is enabled for multipage forms, a draft will be saved automatically each time a user goes from one page to another, regardless of if they are moving from Page 1 to Page 2, or Page 1 to Page 4.

Change Save draft text

Go to your form Settings → Styling & Buttons page and change the Save Draft text.

Change Save draft link to a button

Go to your form Settings → Customize HTML → Submit button section and replace the existing '[if save_draft]' with this:

[if save_draft]<a href="#" tabindex="0" class="frm_save_draft frm_form_submit_style" [draft_hook]>[draft_label]</a>[/if save_draft]

Allow multiple drafts

Since each user can only have one draft at at time, you could still allow your users to create multiple drafts by creating an entry status field.

1. Go to the form builder page.
2. Add a dropdown field and label it as Entry Status.
3. Add Draft and Final as the dropdown options.

A user can indicate if they're submitting a draft or the final entry by choosing the status from the Entry Status dropdown. If the entries are being used in a View, add a filter in the Advanced View settings to only show entries where the Entry Status is equal to Final.

Protect all files uploaded in this form

This file permissions option will appear when the form includes a file upload field. When enabled, uploaded files cannot be accessed directly using the file URL. It prevents files from being indexed and searchable by Google and other search engines.

You may also restrict any files uploaded in a form to be restricted to a specific user role. Anyone without this role will see an error message when trying to access files they don't have permission to view.

Prevent search engines from indexing uploads

This option requires File protection to be enabled and is applied for new files before the entry has been submitted.

If you are using Apache and want to prevent indexing uploads without file protection, you can configure your htaccess file to prevent bots from indexing specific paths.

Copy this form to other blogs

Allows you to copy the current form network-wide when Formidable Forms is activated. This setting only shows up when it's a multisite network.

1. In the form Settings → Form Permissions, select the checkbox Copy this form to other blogs when Formidable Forms is activated.
2. Install and activate Formidable Forms on the new subsite.
3. It will automatically copy the form but not the entries. This option works for both the master site and subsites. It will not copy the form to sites where Formidable Forms is already activated.

Form Scheduling

Set your form to open at a later date or close automatically to stop accepting entries. While open, the form will appear wherever the form shortcode is used. When closed, the 'Form Closed Message' will appear in place of the form.

To set a specific time, use HH:MM format. For example, to open the form at 8:30 AM, use 08:30 for the time. To open at 1:30 PM, use 13:30. This time will use the timezone set in your WordPress settings.

• Open - By default, the form is always open and will accept submissions indefinitely.
• Closed - Set 'Closed' as the form status to manually close the form at any time.
• Schedule - Schedule the form to open and/or close on specific dates.
• Limit Entries - Close the form after a specified number of entries have been collected in the form. This is based on the total count of entries in the form.
• Schedule and Limit Entries - Schedule the form by date and limit by the number of entries in the form. When both a close date and limit are set, the form will be closed based on which is reached first.

Pagination

Formidable Forms Pro includes the option to include a progress bar or rootline in multipage forms. This setting is visible when the form includes at least one page break field.
Default Progress Bar

Default Rootline

Displaying Pagination

By default, a multipage form will hide both the progress bar and rootline from appearing. However, you have three options to choose from.

• Hide Progress bar and Rootline
• Show Progress bar
• Show Rootline

Changing Position

When displaying pagination with your multipage form, you can use the position setting to determine where the rootline and progress bar will be placed. You have four options to choose from.

• Below form title (default)
• Above form title
• Above submit button
• Below submit button

Showing Page Titles

When you show either a Progress bar or a Rootline in your form, you have the option of showing page titles for each page. If you would like to enable this feature, simply check the box labeled 'Show page titles with steps' and then enter a page title for each page in your form. Please note: If you leave any of these fields blank, your progress bar or rootline will have no title for the respective page.

Resulting Progress Bar & Rootline

Hide Page Numbers

By default, the Progress bar or Rootline will show page numbers. To disable this feature, simply check the box labeled 'Hide the page numbers' and then update your form.
Resulting Progress Bar & Rootline

Hiding Pagination Lines

By default, the Progress bar will show a vertical line separating each page in the progress bar. Similarly, the Rootline will show a horizontal line connecting each page in the form. If you would like to hide these lines, simply check the box labeled 'Hide lines in the rootline or progress bar' and then update your form.

Resulting Progress Bar & Rootline

Styling & Buttons

Style Template

Select which styling to use for your form. All Styles that have been created in Formidable → Styles will show up in the Style Template options.

Always use default will be selected as the default option. This will use the Style template that has been marked as the default template. If you choose not to use Formidable styling, your form will adopt your theme styling.

Page Turn Transitions

Choose transition effects that can be used on form load. Select from these options: Slide horizontally and Slide vertically. By default, this is set to None.

If you have set up a multi-page form, select AJAX submit in your form settings for a smoother page turn transition effect.

Submit Button Text

Set the text for your Submit button.

Update Button Text

Set the text for your Update button. This box will only appear if you check 'Allow front-end editing of entries'.

Start Over Button

Use the Start over button to restore the form to its original state before any values were added to the fields. When this option is enabled, it includes an option to customize the button text.

Submit Button Position

Choose to have the Submit button centered, full width, inline, none, or default.

• Default: By default, the submit button will sit below all the fields in your form.
  
• Center: Adds the submit button at the center of the form below all the fields.
  
• Full Width: Set your submit button style width to 100%.
  
• Inline: Align the submit button with all the fields on the same line.
  

Submit Button Logic

The submit button includes options to either conditionally hide or disable it. These settings apply to the submit button on the last page of the form, and not a next button added by a page break field.

Click Use conditional logic, and add settings to hide or disable the submit button. This works just like the field conditional logic. The logic includes the option to hide the submit button until a checkbox is checked.

By default, conditional logic is triggered when the field is changed, which doesn't occur until the cursor leaves the field. To trigger this when a keyboard key is released, you can use this Javascript example instead.

Submit Button Styling

By default, the disabled submit button is displayed at half opacity. To turn off this styling, select the Disable submit button styling checkbox in Formidable → Styles → Buttons.

Restrict email addresses

To restrict certain email addresses in your form, you can follow the steps below:

1. Add an HTML field with a validation message. You could add some CSS styling, if you want.
   
2. Add conditional logic to the HTML field such that it will only show if the email address field is like @gmail.com, @hotmail.com, or @yahoo.com.
   
3. Go to your form Settings → Styling & Buttons page and select Add conditional logic to submit button. Set it to disable the submit button if the email address field is like @gmail.com, @hotmail.com, or @yahoo.com.
   

Messages

Customize your messages that will be seen after the form has been submitted or saved as a draft. You can add any values from the submitted entry to your confirmation message. Use the links and buttons in the right side bar to add fields from your form. You can add text and HTML in this box.

On Submit Message

What will be seen when you submit a completed form.

On Update Message

The message that will appear after a form is updated. This box will only appear if the 'Allow front-end editing of entries' box is checked.

Saved Draft Message

The message that will be shown after a form is saved. This box will only appear when the 'Allow logged-in users to save drafts' box is checked.

Related developer hooks

• Enable saving drafts by default for newly created forms with the frm_new_form_values hook.
• Enable file protection by default for newly created forms with the frm_new_form_values hook.