Formidable Forms – Contact Form Plugin, Survey, Quiz, Payment, Calculator Form & Custom Form Builder
Changelog
6.29
New: Additional validation has been added to prevent people from manipulating amount values when making Stripe payments.
Fix: When updating the Stripe processing message global setting with strings contained backslashes, extra backslashes would get added with each time the global settings were updated.
Fix: Usage tracking code would trigger a str_contains(): Argument 1 must be string, stdClass given warning.
Fix: Credit card fields would appear blank in some previews, like when previewing a Gutenberg block.
Fix: The field options dropdown for the far left field would render underneath the field settings sidebar in rows with a lot of fields.
Fix: An Undefined array key “slug” PHP Warning has been fixed.
Fix: When a missing payment field is automatically added to a form with a payment action, the new field would incorrectly appear below the submit button.
Breaking: The deprecated FrmDb constructor method has been removed.
6.28
New: Required changes to support the new option limits settings in Pro and the new redesigned fields in Views settings.
Performance: The cached license data has been reduced significantly, omitting change log data and data for invalid plugins. The size of the auto-loaded option should be about 40% of its previous size.
6.27
New: Displaying payments is now handled by this plugin, instead of falling back to Stripe, Authorize.Net, and PayPal. In cases where these add-ons were active, the payments table should now appear more modern.
New: A new coupons tab is available on the payments page.
New: Required updates to support a new View-Specific CSS setting in the Visual Views add-on.
New: The submit button will now be enabled when a Square postal code is successfully completed. This fixes issues where the submit button would never get enabled when a Square card field was auto-filled.
New: Many references to old font icons have been removed, removing about 10KB of data from admin CSS.
New: Several styles have been optimized in the generated formidableforms.css file when Pro is not active, helping to reduce file size by removing references to features that only exist in Pro.
Fix: Global custom CSS would incorrectly get added to the formidableforms.css more than once on some sites with multiple styles.
Fix: The style-specific custom CSS setting would incorrectly get output in the formidableforms.css file as CSS variable data.
Fix: The htaccess file included in this plugin is now automatically deleted when migrating to a new plugin version if a request to load CSS is blocked, fixing a conflict on some servers that are not configured to allow overwriting file permissions.
Fix: A PHP warning would get logged when checking data for a ranking field as spam.
Fix: Add-on category counts were not always correct.
Breaking: Many modern PHP functions are now being used including str_contains, str_starts_with, str_ends_with, array_key_last, and array_key_first. If you are using both a WordPress version older than 5.9, and a PHP version lower than 8.0, this will introduce fatal errors. Note that the minimum required WordPress version is already set to 6.3.
Breaking: The deprecated functions FrmFieldCaptcha::captcha_size, FrmFormsHelper::should_use_pro_for_ajax_submit, FrmFormsController::add_form_style_tab_options, and FrmFieldType::get_select_atributes have been removed.
Breaking: The deprecated FrmFormsHelper::actions_dropdown function and actions-dropdown.php view file have been removed.
An unused FrmTransLiteSubscriptionsController::list_subscriptions_shortcode function and its related view file have been deprecated.
6.26.1
New: The cached data for license checks is now set to autoload to help reduce calls to the database, and an option check for a request lock has been moved so it only happens when the option data has expired. These changes should help with performance.
New: SVG icon updates have been made to avoid use of the deprecated xlink:href attribute.
Fix: Field step settings were changed to only accept numbers in last release, causing issues with “any” as a value.
Fix: Bootstrap dropdowns would not properly initialize for fields loaded with AJAX in long forms, preventing access to the more options dropdown, hiding the option to delete a field.
Breaking: Old logic that would trigger blur events for inputs with no value set with the onblur attribute has been removed.
