Ajax Submit

Ajax submit has been added. It can be enabled on a form-by-form basis. To enable ajax submit, go to the settings page for each form, and check the box to “submit this form with ajax.” File uploads will not yet be submitted via ajax.

Increased Security

Security has been increased. First, another vulnerability was found in Open Flash Charts. The safest option was to completely remove Open Flash, so all graphs will now use Google charts. Second, when a custom display is used to show entries, any included javascript will be automatically stripped before displaying on the page. If you are intentionally included javascript in your submitted entries, you can retain it in the custom display with keepjs=1. For example, if your field id is 125, you would use [125 keepjs=1] in your custom display.

Field Stats within Ranges

Added option to limit by ranges in the frm-stats shortcode. For example, this shortcode would only count entries where the value of field 45 was between 1 month and 3 days ago:
0
Dates, numbers, and text values can be used for the greater than and less than options. See more examples.

Additional Field Options

Dropdown fields include a checkbox to allow multiple options to be selected in that field. This switches the field to a multi-select field. The size of this field can also be customized in the field options.

The dropdown to “Allow Only One Entry for Each” field has been modified. All form fields have been removed from this dropdown, in favor of only using the “unique” checkbox in the field options.

Customizing the unique error message is now possible without custom code. It has been added as a global setting as well as an individual field setting.

Email Message Customization

Added buttons to insert default HTML or plain text for those who wish to modify the default message without starting from scratch. For more information on customizing the default message, see this page.

Allow external short codes in the email recipients box.

Additional Content Customizability

Added striphtml=1 for use within custom displays. This allows you to strip any HTML from user-submitted content before displaying it on your site.
Added shortcode option to get the field description with [125 show="description"]. This new option can be used in custom displays, email messages, or anywhere else you can insert field shortcodes.

You may now delete Formidable entries that were used to create post content without also deleting the created posts. Use the new “delete without post” link to delete only the entry. This link can be found on the view and edit entries pages in the back-end.

Custom CSS can now be added directly into the visual styling page in the Formidable global settings. Any CSS added here will not be overwritten when updating the Plugin.

Other Changes and Additions

• Fields with separate values have an extra column on entries page to show the saved value
• Added a link to the uploaded file in the entry edit form
• Added “like” and “not like” options to the conditional logic for hiding and showing fields
• Switched section headings and page breaks to use h3 tags by default instead of h2
• Switched rich text fields to default to TinyMCE
• Switched the field options bulk edit to use the admin ajax url to minimize plugin conflicts
• Show the taxonomy name even if it is not linked to a post
• Fixed post content replacement when entry is updated instead of only on creation
• Moved all stripslashes and unserializing to the point the data is retrieved from the database
• Added quotes around the menu position number to minimize menu position conflicts with other plugins
• View the full Changelog

We are continually working to reduce the number of questions being asked by simplifying and adding functionality. A common, time-consuming problem users are running into during the form-building process, is with the email content. We’ve seen many questions from those who just want to mildly tweak the default message, but don’t want to rebuild it in it’s entirety. There is now a way to do so. Two buttons have been added in the sidebar box for “Default HTML” and “Default Plain.” These buttons will insert a generated message with the fields that are currently in your form, as the default message would look if it were sent out at that moment.

Another common question is in regards to where to place any custom CSS. We generally instruct that it be placed in your theme’s style.css file, but there are those who update their themes and lose customizations. We have added a box in the Formidable -> Global Settings -> Styling page, where any CSS can be added and saved with other Formidable settings. CSS added to this “Custom CSS” section will not be overridden when updating Formidable Pro.

The frm-stats shortcode has also been beefed up to not only allow a single value to be specified, but also ranges of values. For example, if you have a date field in your form, and would like a value counted only within a certain date range, that is now possible with a shortcode that looks like this:
0 (include values from field 50 when the date field(id of 45) is between 2013-02-01 and 2013-03-01)
0 (include values from field 50 when the date field is between 1 month and three days ago)
0 (include values from field 50 when the date field is within the last month)

You can see a full list of changes in the change log.

Since this is a beta version, it is not available via automatic update, but can be downloaded from the downloads page and installed manually.

Second, if you are using any graphs, be aware they will all switch to Google graphs. More security vulnerabilities have been uncovered in Open Flash charts, so we decided it would be safest to completely remove them. When updating manually, you should delete the whole plugin before installing the new version so the vulnerable files will be removed from your site. The WordPress auto-update feature will automatically delete the old plugin files before installing a new version.

Lastly, of course you want to know what features have been added. First and foremost: AJAX submit! Dropdown fields have an added checkbox to change into a multiple box.

More security has been added for those accepting untrusted user submissions and displaying them using custom displays. All javascript will be automatically stripped when displaying. This can be overridden by adding keepjs=1 to the field shortcode [25 keepjs=1]. Also, some users have reported the desire to strip all HTML from user submissions as well. Adding striphtml=1 will remove any HTML added into that field. Both of these do not permanently change the original submission, but only remove the javascript and HTML for display purposes only.

You can see a full list of changes in the change log.

Since this is a beta version, it is not available via automatic update, but can be downloaded from the downloads page and installed manually.

1. Install and activate the Progress Bar plugin by Chris Reynolds
2. Build your multi-page form in Formidable Pro using the “page break” field type to indicate where each page will start
3. Add new “HTML” fields before your “page 1″ fields and directly following all “page break” fields in your form. This assumes you want the progress bar at the top of your pages, but you can add them anywhere you would like progress bars to be displayed in your form.
4. Add progress bars to your newly created HTML fields by clicking on the “field options” bar on each of your HTML fields. You can type the Progress Bar shortcode directly in the “content” box found in these field options. For demos of the different progress bar types, colors and options with their associated shortcodes, click here.
5. Your HTML field options should look something like this
   
   
6. If you would also like to add a progress bar to the success message, you can do so on the form setting page as shown here:

That’s it. The result should be a progress bar at the top of each page of your form indicating the total progress. Here is a screenshot of what my overall form looks like on the form builder page and an example of page 2 of my form:

Added Options

Options have been added into the “Field Options” for each signature field. The options include changing the height and width, naming the tabs, or even removing them.

Clean up

Since a signature field should default to a signature, the drawing tab is now the default. The field to type into has been moved inside the “Type It” tab to further clean the field up, and validation removed from the script and moved into Formidable to make it more seamless. The size of the signature box will scale down depending on how much room is available for it, and display the signatures in the same size they were generated.

This update is available via auto-update from your WordPress admin.

Full Change log

Email Notification Overhaul

Conditional logic in now available on email notifications. This logic is similar to the conditional logic on showing and form fields. There is no longer a difference between autoresponder and admin notifications, and you can have any number of email variations. Of course the inline logic still works in the email messages, as well as the [default-message] shortcode which has been extended to work in any email.

Multiple Files per Field

Upload files have a new option to “allow multiple fields to be uploaded to this field.” Checking this box presents users with a new upload field each time they select a file, the same way the upload works in our help desk.

These images can be displayed in custom displays in a couple of different ways. First, the easy way is to automatically include the HTML with [25 html=1] (where 25 is the ID of the upload field). Second, is the more advanced option to define your own HTML.
<img src=”[25 sep='" /><img src="']” />

Custom Displays switched to Custom Post Type

Over the next year or so, we would like to phase out all custom database tables in favor of custom post types. We’ve started this process with custom displays. Not only does this eliminate an extra database table, but also inherits many extra benefits including revisions, previews, bulk editing, and saving as draft. The shortcodes will continue to work, or you can simply use the page generated for your custom display. These custom displays are not listed anywhere on the front-end of your site.

The “Customized content” box on the “Create posts” settings tab will now be saved to the post content if no field is selected to be used as the post content. In this case, changes made to the post content directly on the WP posts page will not be reflected in the Formidable entry or on the front-end of your site.

Additional Shortcodes

A few shortcodes have been added to help make simple and complex applications easier.

• Get a single value from an entry.
• Set a value to use in [get param=something]
• Show all detail for a single entry in the same format as the default email message.

Extended Conditional Logic

The conditional logic for showing and hiding fields now includes hidden, text, number, email, website, and time fields. It also supports selecting a blank option to make it possible to show one field if anything has been selected in another instead of requiring a specific option to be selected.

Other changes that may affect your site

Two additional changes may affect the way your form and calendar custom display are currently displayed. First, the generic css classes like “text” and “date” have been removed from input fields. These were originally added for future use, but they have been causing too may problems with theme styling conflicts. This may affect you if you added custom styling using these classes, or if you were depending on similar css from your theme.

Localization has been added to the custom display calendar, so it will now start on day of the week selected on the WordPress Settings -> General page. The calendar previously started on Sunday, but the default WordPress setting is Monday. Please check your calendar to make sure it starts on the day you would like.

Full Change Log

v1.06.07

Version 1.06.07 is a bug fix release.

• With each update, we have had a handful of people who get stuck in an update loop, unable to get the pro version installed. From here on out, the automatic update feature will be smoother with only one-step updates.
• Added mb_split fallback for servers without mbstring installed. This function is used to truncate text throughout the plugin.

Full Change Log

The parts that need the most widespread testing across multiple sites and servers, are the new custom displays and email notifications. Feedback and bug reports are welcome. Please let us know in the help desk about any bugs you may come across!

Full change log

Download and manually install

Multiple file upload can be enabled by opening the field options for any upload field and checking the box to “allow multiple files to be uploaded to this field”. This will enable a file upload similar to the one seen in our help desk.

These images can be shown in custom displays in a couple of different ways. First, the simple option that automatically adds the HTML to show an image:
[25 html=1]

Alternatively, you can customize this HTML in an advanced way with something like this:
<img src=”[25 sep='" /><img src="']” />

The email notifications are in the same place as before, but are formatted a bit differently to match the updated custom display format with the list of fields in the sidebar instead of in drop downs above each field.

We are excited about these changes and the elimination of more custom code that we have been recommending for conditional email routing. Please let us know in the help desk if you run into any issues.

Full change log

Download and manually install

A new shortcode has been added to assist with getting values from forms. This is intended for use as a default value to populate fields with values from other forms. There are a few different ways to specify the correct entry to get the value from: entry id, user id, or ip.
[ frm-field-value field_id=25 user_id=current]
[ frm-field-value field_id=25 entry_id=140]
[ frm-field-value field_id=25 ip=1] (Use the current user’s IP)

In a custom display:
[ frm-field-value field_id=25 user_id=[28 show=ID]]
[ frm-field-value field_id=25 ip="[ip]“]

Generic classes from input fields like “text” and “date” have been removed to alleviate conflicts with some themes. For any who are using custom styling on input fields using these classes, be sure to update them!

Full change log

Download and manually install

PayPal out of Beta

The PayPal add-on is now official. It’s been updated to work well with Formidable changes including separate values and redirecting. Fields using separate values can now be used in the conditional logic, and IPN notifications will work correctly with the latest version of Formidable.

AWeber Fixes

The AWeber add-on has had a few fixes as well including a W3 Total Cache conflict resolved, and updating the authentication code on the settings page is supported. All the AWeber class names have been updated to avoid potential conflicts with other plugins.

Registration Updates

• Added the frmreg_new_role filter on the user role new users will be created with.
• Only show user meta one time on the profile page if multiple forms are being used for the same user meta.
• Fixed bug with first and last name display names that was piecing the display name together incorrectly.