Formidable Forms v6.35

Last updated on September 9, 2026 by Mike

New: A range slider's Default Value setting is now split into separate Start Value and End Value inputs, one for each handle. Either one accepts a shortcode instead of a number, and both are kept within the field's minimum and maximum. A single handle slider keeps the one Default Value box it has always had.
New: Address field subfields can now be used in text calculations, in the same way name field subfields already could.
New: More than one Square action can now be added to a single form. Conditional logic on form actions decides which one runs, so the one per form limit that applies in Lite is lifted while Pro is active.
New: Dates in a CSV import are now read from many more formats. The other rows in the file, the date field's own format setting and the WordPress date format are all used to work out whether a value is day first or month first. Dash and dot separated dates continue to be read day first, and slash separated dates month first.
New: A new frm_jquery_ui_base_url filter has been added for changing the CDN that jQuery UI theme stylesheets and i18n scripts load from.
Performance: Forms with a lot of conditional logic now open faster in the form builder.
Fix: Settings that point at another field would lose their reference when a form was imported and the field they point at had not been imported yet. Conditional logic, lookup watching, quantity product fields, summary field exclusions, lookup values, dynamic field sources, time range linked dates and section membership are all remapped correctly now.
Fix: Lookup fields would keep pointing at the original form rather than the copy when a form was duplicated.
Fix: A read only calculated Number field using the Currency format would submit an empty value when it had both a prepend and an append box and a comma decimal separator.
Fix: Calculation details would get lost when a second set of calculations was merged in, which happens when there are multiple forms on a page, or when moving between pages of a form submitted with ajax.
Fix: The datepicker would load with no styling at all in WordPress 7.1, which updated jQuery UI to 1.14.2 and left the theme stylesheet returning a 404. Theme fields are now loaded from the Cloudflare CDN instead of from Google. This only affected sites using the jQuery UI datepicker with a theme other than the default one. The bundled stylesheet now always loads underneath the theme, so an unreachable theme still leaves a usable calendar.
Fix: Date styler settings would only partly apply to the Flatpickr calendar, leaving a blue border on the selected date and a blue date range whatever colors were set.
Fix: Flatpickr would hand phones the browser's own date input, which silently dropped blackout dates, day of the week restrictions and date ranges. The calendar is now used on mobile as well.
Fix: A locale with no matching Flatpickr localization file would request a file that does not exist and log a 404.
Fix: The slider field background would not match the default value in the form builder preview, and would jump to the correct value when editing an entry instead of showing it on load. A gap larger than the difference between the minimum and maximum is now limited to that difference.
Fix: The See more dropdown on the applications page would not open when Bootstrap 5 was loaded.
Fix: Nested conditional shortcodes would close on the first closing tag rather than their own, so a stray [/if] or [/foreach] tag could show up in the output.
Fix: An [else] shortcode placed inside a nested condition would be treated as belonging to the outer condition, so the wrong content was displayed.