Today we are happy to announce that Caldera Forms 1.3.1 is here. This release fixes some important bugs, and provides more reliable form validation across multiple types of devices and browsers. Today we are also releasing a new version of the users add-on for Caldera Forms. You can now add all three of this add-on’s processors more than once, though only one will run. In addition you can now enable password strength enforcement.
It is important to be aware of two changes, Caldera Forms which we recommend you testing on your staging or local test environment in advance of updating. They are listed below.
As a brief sample of what is in store, here is a gallery of screenshots of the new changes, and screencasts which were built using the new version.
Pretty slick gallery right? It’s powered by the FooVideo add-on for FooGallery, which we helped build:)
Caldera Forms 1.3.1
This new version of Caldera Forms, makes two big changes to make it more reliable. The first is that we have implemented the parsley.js library for in-browser validation. Relying on this popular project will give us more stable validation moving forward.
Please note that field validation messages are slightly different in this version of Caldera Forms. We have done our best to stick to keep things consistent with how Caldera Forms has always appeared. Please make sure this new validation looks right with your theme by testing with some intentional errors first.
The other big change in this release is that we have moved processing to new endpoints. This has been done to avoid misusing admin-ajax and pave the way for some interesting new features in the future. We have taken extra care to make sure that permalinks are flushed after updating or installing, so our new endpoints work. Please be sure to check that AJAX submissions work after updating and if not, please flush your permalink settings manually by re-saving them from the WordPress admin.
In addition, we have also added the ability to set orderby field and order direction for auto-populated fields from the field editor UI. To simplify the setting for file fields, you can now specify allowed field types with or without dots.
This release also adds the ability to update the plugin to the latest development version on Github using the for the Github Updater Plugin and improved form export significantly.
Other bugs we have fixed include:
- Bug preventing mailer attachments when returning from Paypal.
- Bug where enter key could trigger submit from any page of a multi-page form in some circumstances/ browser.
- Recaptcha settings link opening in same window.
- Bug where CSS was being loaded in footer in some cases.
- Visual issue where datepicker fields in Twenty Fifteen theme showed full width.
New filters:
- caldera_forms_processor_value filter for changing value of a field from a processor.
- caldera_forms_manage_cap filter for managing all capabilities by context.
- caldera_forms_script_urls and caldera_forms_style_urls filters for modifying/ removing scripts and styles before enqueuing.
Caldera Forms Users 1.3.0
This new release of our popular users add-on provides two highly requested new features. These features are the ability to add the users processors more than once to a form, and the ability to enforce password strength requirements.
Previous versions only allowed you to add one instance of each of the three processors to the form. This restriction was put in place beacuse it is only possible to login or register one user at a time. The new version allows you to add as many instance of the processor as you want, but only one of them will actually run. This allows you to use conditional logic to choose which instance of the processor to use.
The other exciting new feature of this plugin is the ability to enforce strong password strength. We have implemented the same JavaScript as WordPress core does for evaluating password strength. You can choose to allow any passwords, medium strong passwords or very strong passwords.
In addition, you can now customize the text of the confirm password field when that is used.