Gravity Forms | O Melhor Plguin de Forms para WordPress | Construtor de Formulários

Gravity Forms | O Melhor Plguin de Forms para WordPress | Construtor de Formulários 3.0.1 Nulled

Sem autorização para baixar
- Fixed a PHP warning that occurs when the [gform_email_field_rejectable_values](https://docs.gravityforms.com/gform_email_field_rejectable_values/) filter returns a large array of values.
- Fixed an issue with payment amount calculation that does not take dynamically populated product prices into account in certain situations.
- Updated `gf_feed_processor()` to accept an optional `$add_on` parameter.
- Added the [gform_is_feed_error_retryable](https://docs.gravityforms.com/gform_is_feed_error_retryable/) filter, which can be used to prevent a feed remaining in the queue for another attempt if an error occurred.
- AF: Updated `GFFeedAddOn::maybe_process_feed()` to use separate background processors for each add-on, so pausing the queue on a feed processing error doesn't impact other add-ons.
- Added the `gform_pre_log_message` action hook to allow developers to do an action before a message is logged, whether or not logging is enabled. Credit: Gravity Wiz Team.
- Added alt attribute to the QR code image in the REST API settings for improved accessibility.
- Fixed an issue where a programmatic submission of a multipage form page progresses to the next page when the next button is hidden/disabled by conditional logic.
- Fixed contrast errors triggered by save buttons and error messages throughout the settings pages.
- Fixed PHP warnings that occur when editing a page that includes a scheduled form with an end date in the past.
  • Curtir
Reações: lorus
- Added security enhancements.
- Updated the background processor to dispatch queued tasks on shutdown to improve performance.
- Updated messages about functionality that will be removed or deprecated in future versions to 4.0 instead of 3.1, to reflect our new [version numbering system](https://docs.gravityforms.com/version-numbering/).
- Updated the logic that determines whether an update — including for add-ons — can be installed automatically, to ensure compatibility with the change to the [version numbering system](https://docs.gravityforms.com/version-numbering/).
- Updated the minimum WordPress version (for support) on the System Status page to 6.8.
- Fixed deprecation notices for the `seems_utf8()` function in WordPress 6.9.
- Fixed an issue where some uploaded files are not attached to notifications when stored outside the default form/year/month folders.
- Removed the invalid maxlength attribute from class-gf-field-time.php.
  • Curtir
Reações: lorus
- Updated the logic that determines whether an update — including for add-ons — can be installed automatically, to ensure compatibility with the change to the [version numbering system](https://docs.gravityforms.com/version-numbering/).
- Fixed deprecation notices for the `seems_utf8()` function in WordPress 6.9.
- Updated the minimum WordPress version (for support) on the System Status page to 6.8.
  • Curtir
Reações: lorus
- Fixed an issue where some uploaded files are not attached to notifications when stored outside the default form/year/month folders.
- Added a check for minimum requirements compatibility when an update is available.
- Added a hook for [`gform_before_delete_field`](https://docs.gravityforms.com/gform_before_delete_field/) in the init_ajax() function.
- Added security enhancements.
- Fixed a bug that prevents the "Embed Form" functionality from pre-selecting the correct form in WordPress 6.9.
- Fixed a bug that prevents the Results page from displaying in WordPress 6.9.
- API: Added the GF_Field::$is_payment property, so developers can indicate if a field is used to capture payments. This can be used by features (e.g. Save and Continue) to exclude the field without checking for specific field types.
  • Curtir
Reações: lorus
- Fixed a bug that prevents the "Embed Form" functionality from pre-selecting the correct form in WordPress 6.9.
- API: Added the GF_Field::$is_payment property, so developers can indicate if a field is used to capture payments. This can be used by features (e.g. Save and Continue) to exclude the field without checking for specific field types.
- Added a hook for `gform_before_delete_field` in the init_ajax() function.
- Added security enhancements.
- Added Stripe Membership and Stripe Event Sponsorship templates to the Template Library.
- Added security enhancements.
- Added copy buttons to the Consumer Key and Consumer Secret when adding a new REST API Key.
- API: Deprecated the JS-based GFMergeTag, which will be removed in Gravity Forms 3.1 Use gform.mergeTags instead.
- Fixed an issue introduced in 2.9.21 where the selected file is not saved for a single File Upload field when editing an existing entry.
- API: Removed `GFFeedAddon:😛aypal_fulfillment()` legacy method.
  • Curtir
Reações: lorus
- Fixed an issue introduced in 2.9.21 where the selected file is not saved for a single File Upload field when editing an existing entry.
- Added security enhancements.
- Added a new setting to the Honeypot Field to check the time it takes to submit a form and mark the form as spam if the submission is too fast.
- Updated account/license links to point to the new Gravity account site at [https://account.gravity.com/](https://account.gravity.com/).
- Fixed Mailchimp capitalization in Survey Form template and elsewhere.
- Fixed an issue that can cause the `gform_update_feed_active` action hook to fail if the hooked action calls $wpdb.
- Fixed an issue where a page with multiple forms including file upload fields will retain and display submitted files from differing forms.
- Fixed an issue with the timing of the multi-file upload handler sending the headers that prevents the Chained Selects field CSV upload completing.
Voltar
Top