Skip to content

Releases: Strategy11/formidable-forms

v6.11.1

09 Jul 14:22
d58d55b
Compare
Choose a tag to compare
  • New: Screen reader text has been updated on some admin pages to improve accessibility.
  • New: Hover styling has been updated for modal close icons to improve user experience.
  • Fix: The way Popper scripts are registered have been updated to help avoid a new conflict introduced in a recent WP Bakery update.
  • Fix: The reCaptcha settings name was missing in a global settings string.
  • The minimum supported version of Formidable Pro has been bumped to version 6.0.
  • The function FrmAddonsController::is_license_expiring has been deprecated.

v6.11

19 Jun 14:08
a0698e8
Compare
Choose a tag to compare
  • New: Field errors added when validating with JavaScript would use field IDs instead of field keys. This has been updated to use field keys for consistency.
  • New: When a layout class option is selected, any previous layout classes that would cause a conflict will now be automatically removed.
  • New: An optimization has been added to help reduce form builder load times for forms with many HTML or Rich Text fields.
  • New: A styling update has been made to make field placeholder font sizes more consistent.
  • New: Stripe actions included in this plugin now support a Recurring Payment Limit setting. When this setting is defined, and the number of payments has been reached, the subscription will be cancelled automatically.
  • Fix: References to JavaScript map files have been removed from bootstrap and popper scripts to prevent 404 error messages that appear when using Safari.
  • Fix: An Undefined array key PHP Warning would get logged when trying to remove fields using the frm_available_fields or frm_pro_available_fields filters.
  • Fix: Form previews would include two conflicting title tags in the source HTML.
  • Fix: A small update has been made to properly support sending data for repeated API actions.
  • Some old CSS styles have been removed, helping to reduce file size.
  • An old TTF file used for icon fonts has been removed as it was only required for supporting Internet Explorer and is no longer required, helping to reduce overall file size.

v6.10

29 May 13:28
878ed01
Compare
Choose a tag to compare
  • New: Field data for shortcodes is now stored in memory and reused on the settings page and form builder page for a significant page load speed improvement for forms with a lot of fields.
  • New: XML import has been updated to support mapping field ID changes when importing a map view and new calendar view settings.
  • Fix: Payments using a currency that uses a comma as the decimal separator would have an incorrect amount value when the amount value had a single decimal point like 11,5.
  • Fix: Field error elements would inconsistently use either IDs or field keys in their ID values. An update has been made to use always use field keys.
  • Fix: In some cases, a Stripe redirect would happen after failing to create an entry, resulting in an unexpected redirect to stripe.com.
  • The minimum supported PHP version has been updated to 7.0, ending official support for PHP 5.6.
  • The frm_summary_email_content_args hook has been moved to where it is now filtered for all types of email summaries.
  • Several deprecated PHP functions have been removed including FrmFormsHelper::template_install_html, FrmFormsHelper::available_count, FrmFormsHelper::builder_submit_button, FrmFieldsHelper::get_shortcode_tag, FrmFieldsController::include_single_field, and FrmFormsController::new_form.
  • Several deprecated front end JavaScript functions have been removed including frmFrontForm.goingToPreviousPage, frmFrontForm.hideOrShowFields, frmFrontForm.hidePreviouslyHiddenFields, frmFrontForm.checkDependentDynamicFields, frmFrontForm.checkDependentLookupFields, and frmFrontForm.loadGoogle.
  • Some front end JavaScript code for supporting Internet Explorer has been dropped, helping to reduce the size of JavaScript required on the front end.

v6.9.1

06 May 16:03
977644c
Compare
Choose a tag to compare
  • New: Some data used for field settings is now stored in memory and reused in order to significantly improve performance in the form builder for forms with a lot of fields.
  • Fix: Rootline and progress bar elements would not appear when using some position settings with the new submit button field.
  • Fix: An invalid argument supplied for foreach() error has been fixed when truncating unexpected values.
  • Fix: Submit button fields were appearing by mistake in WooCommerce products.
  • The parser for serialized string data has been optimized to be approximately 30% faster than before.
  • Some old deprecated code has been removed including the FrmPointers and FrmDbDeprecated classes, FrmAppHelper::sanitize_array, FrmAppHelper::expiring_message, and several methods in FrmEntryValidate.php.
  • Old polyfill code for supporting old versions of Internet Explorer have been removed from front end JS, reducing file size.

v6.9

17 Apr 13:49
d8d16df
Compare
Choose a tag to compare
  • New: A new onboarding wizard has been added to help improve the initial set up process.
  • New: Submit buttons can now be dragged in the form builder like a field. The submit button may be dragged into the last row beside fields.
  • New: data-invmsg and data-reqmsg HTML attributes used for JS error validation are no longer included for hidden fields by default to help reduce the amount of HTML required for a form. A new frm_field_validation_include_data_attributes filter has been added to modify the default behaviour.
  • Fix: A fatal error would occur on the visual styler page if the API request for style templates had failed.
  • Fix: The shortcode list has been updated for calculation field options so field IDs are now still visible for fields with long names.
  • Fix: The sortable indicators were missing for the forms and entries list pages. The accessibility of the sorting indicators has also been improved.
  • Fix: A confirmation field wouldn't validate with JS when left empty.
  • Fix: Tooltips will be deleted now after an action is deleted to fix an issue with old floating tooltips.

v6.8.4

27 Mar 17:27
7f9b3d2
Compare
Choose a tag to compare
  • New: Cloudflare Turnstile has been added as a new Captcha option type in Global settings.
  • New: A new filter has been added to enable support for bulk editing options for a Ranking field.
  • New: The trigger to save draft entries has been updated to a button in new forms.
  • New: A new frm_after_generate_csv action has been added. This can be used to track which entries have already been exported as CSV to avoid exporting an entry more than once.
  • Fix: hCaptcha was not properly resetting after clicking the previous button and returning to the page with the hCaptcha field.
  • Fix: A trim(): Passing null to parameter #1 PHP Deprecated message has been fixed.
  • Fix: Checks have been added to avoid fatal errors when trying to extend the time limit when the function is disabled.
  • Fix: A Creation of dynamic property FrmProEddController::$save_status is deprecated PHP Deprecated message has been fixed.
  • Fix: Icons were missing for collapsible sections in the visual views builder.
  • Monthly summary emails will not longer get sent when there are no new entries to report on.
  • The global JS function frm_add_logic_row used on admin pages has been removed.

v6.8.3

06 Mar 15:37
d5c887a
Compare
Choose a tag to compare
  • New: HTML field descriptions now support the shortcode pop up used in email actions.
  • New: Exported posts from entries will now include <term_parent> tags when applicable.
  • New: The collapsible sections used in the visual styler are now more accessible, including new aria-expanded attributes.
  • New: Error messages should now be more descriptive. "This field" and "This value" strings will now be dynamically replaced with the name of the field. To partially revert this, a new frm_error_substrings_to_replace_with_field_name filter has been added as well.
  • Fix: Form objects with missing option data would trigger fatal errors during various actions, including when deleting the form.
  • Fix: HTML tags would get stripped of most HTML when displayed in a summary for a unprivileged or logged out user.
  • Fix: A Uncaught TypeError: Cannot access offset of type string on string error has been fixed when checking for add-on data.
  • Fix: License expired emails would get incorrectly sent for rate limited API requests.
  • Fix: Some color style settings would output invalid RGB values when using a RGB color as the style setting value.
  • API requests sent for retreiving add-on and template data will now happen less frequently.
  • A few old deprecated global JavaScript functions have been removed including frm_resend_email, frmOnSubmit, and frmDeleteEntry.
  • Some old CSS rules using -webkit- and -moz- prefixes have been removed, helping to reduce CSS file size.

v6.8.2

15 Feb 14:48
44f5be3
Compare
Choose a tag to compare
  • Fix: The process of connecting an account to formidableforms.com would fail in some web browsers.

v6.8.1

14 Feb 18:47
26f2763
Compare
Choose a tag to compare
  • Security: A nonce check was missing on an action for dismissing a call to action on the global settings page.
  • New: Bulk action checkboxes on the form list now include screen reader text for improved accessibility.
  • Fix: Some undefined property PHP warnings when displaying Summary fields were fixed.
  • Fix: Two search buttons would appear on the Entries list page on some websites because of a styling issue.
  • Fix: The action limit error message would always show the action limit as one.

v6.8

25 Jan 16:24
b8a557b
Compare
Choose a tag to compare
  • Security: Nonce validation was missing when saving changes on the form settings page.
  • New: A new dashboard landing page has been added with a list of recent entries, access to your inbox, and a payment summary, all in one place.
  • New: New fields will no longer appear on the front end until the form builder is saved. This way a form can be used without partial incomplete changes while a form is being worked on.
  • New: An HSL color value can now be used in the visual styler. Previously these values would be prepended by # and PHP warnings would cause styles to break.
  • New: Stripe subscriptions will now cancel at period end by default instead of cancelling immediately. This can be reverted to the previous behaviour using add_filter( 'frm_stripe_cancel_subscription_at_period_end', '__return_false' );.
  • New: Summary emails will no longer send by default on multisite for sites that are not the main site.
  • New: Summary emails can now be disabled from your profile on your Formidable Forms account for Pro users.
  • Fix: On some sites, while using Google Chrome, some style card menu options would be missing. This includes the option to Delete a style or to Set a style as default.
  • Fix: Long forms loaded with AJAX were loading in smaller batches than intended, usually pulling only a few fields at a time. This has been restored to the intended batch size of 15 fields at a time.
  • Fix: A styling issue in some search search inputs has been fixed.
  • Fix: The view payment page was appearing blank, and table column options were missing when editing a table view.
  • Fix: An error message wouldn't properly appear when using a 3D secure card and failing the payment.
  • Fix: A subscription with a failed payment would incorrectly redirect like a confirmed payment.
  • Fix: The toggle to disable form styling would still appear active when disabled through the Manage Styling global setting.
  • Fix: Encoded characters would appear in plain text summary emails.
  • List tag types include ul, ol, and li are now allowed in form input HTML by default.
  • Form input HTML will no longer be filtered to strip most HTML on display if the entry was created by or edited by a privileged user.
  • Summary emails are no longer sent when there are no new entries.