Notas da versão 4.0.2: 1 melhoria3 correçõesMostrarOcultar
Melhoria
The woocommerce_gforms_item_meta_rows filter receives a fifth argument, $context: 'cart' for the cart and checkout, 'order' for the order line.
Correção
Cart and order item details show without a deprecation notice under Gravity Forms 3.0 and later.
Repeater fields show one line per row under the field's label in the cart, checkout, order screen, emails and My Account, without a PHP warning.
The Item meta field pickers list only fields that hold entry data, and their selections are readable.
Versão 4.0.1
Notas da versão 4.0.1: 1 correçãoMostrarOcultar
Correção
Product pages built with WooCommerce's Add to Cart with Options block, as in the Purple theme: totals follow the options and the chosen variation, a form with a Total field adds priced options to the cart, and editing a cart item keeps its quantity.
Versão 4.0.0
Notas da versão 4.0.0: 8 novidades9 melhorias11 correçõesMostrarOcultar
Novidade
Form settings. Set a form's WooCommerce options once, on the form's new WooCommerce tab. Each section of a product can follow the form or use its own settings; existing products keep their own, so nothing changes on update.
Attach a form to product categories and tags. The form's tab lists every product using it, and a Form column for the Products screen (Screen Options) shows and filters by form.
Choose which form fields show with the item in the cart, checkout, emails and the order screen, or show one line built from merge tags.
Product field map. Set the cart item's weight, dimensions and quantity from form fields; the values reach the order, so shipping labels use them.
Add products with a form through WooCommerce's Store API, for headless stores and AI shopping assistants.
Cart items show an Edit link, and the block cart shows each answer on its own line.
Structured data takes a flat price or a price range, added to the product price or replacing it.
Hide the form's Gravity Forms Total field on the product page (Display: Total field).
Melhoria
Requires WooCommerce 11.0, WordPress 6.9 and Gravity Forms 2.9.
The Gravity Forms panel in the product editor is rebuilt. Custom admin CSS or JavaScript written for the old panel needs updating.
Gravity Forms Total fields no longer show under cart and order items. To show them: add_filter( 'woocommerce_gforms_hide_total_field', 'return_false' ).
Product page totals include tax the same way the product price does.
Multi-part fields marked wc-gforms-hide-from-email are hidden in the cart as well as on the order.
No database query on every page load to find products with forms.
Woocommerce_gforms_field_display_text receives ( $display_text, $display_value, ... ) on orders as in the cart; a snippet written for the old order-side order needs its first two arguments swapped.
New filter woocommerce_gforms_resolved_settings( $settings, $product_id, $context ) filters a product's final settings after product and form settings are merged.
Removed the WooCommerce 2.x compatibility layer (WC_GFPA_Compatibility, wc_is_21x, is_wc_version_gte_2_2, is_wc_version_gte_2_3, is_woocommerce_active, WC_Dependencies) and the JavaScript function get_gravity_forms_price.
Correção
A product can only be added to the cart with its own form filled in: not with an inactive or deleted form, another form's submission, or a bare add-to-cart link or Store API request.
Order Again: a guest order's answers need its order key, a product without a saved entry asks for its options, and "resubmit" mode works without errors.
Editing a cart item keeps its quantity, including products sold individually and quantities set by a form field.
Saving an order's items keeps stock reduced by a form field.
Redirect and page confirmations no longer stop the item reaching the cart.
Theme add-to-cart buttons without WooCommerce's button class add the item to the cart.
Items in carts update when a form's prices, choices or conditional logic change, and country conditional logic saved before Gravity Forms 3.0.3 matches again.
Product page totals on variable, grouped and page-builder products and multi-page forms.
The text before and after the price shows once, and only on the storefront.
Errors with a non-numeric structured data price, and with merge tags whose order was deleted.
Dynamic Pricing live prices, Quick View and WooCommerce Bookings.
Versão 3.8.6
Notas da versão 3.8.6: 3 melhorias1 correçãoMostrarOcultar
Melhoria
Tested up to WooCommerce 11.2
PHP 7.4 is now declared as the minimum supported version, matching WooCommerce
Dynamic Pricing 4.0 compatibility: product-page totals use Dynamic Pricing's public function, so product and category tiers now apply at quantity 1. On Dynamic Pricing 3.6.x the existing behaviour is unchanged.
Correção
The "Enable Dynamic Pricing?" setting is no longer hidden or reset to No when Dynamic Pricing 4.0 is active.
Notas da versão 3.8.5: 1 melhoria5 correçõesMostrarOcultar
Melhoria
Tested up to WooCommerce 11.1
Correção
After a form attached to a product was edited, viewing the cart or checkout could send that form's notifications and create a Gravity Forms entry for every affected cart item, on every page view, and ordering again with the "revalidate" setting did the same. Checking whether a saved entry is still valid submitted the whole form. It now only validates it, and nothing is saved or sent.
That check also rejected cart items that were still valid - list fields, numbers in a decimal-comma format, and fields set to allow no duplicates (the value matched the item's own entry) - and on a form with several items in the cart, one item's result could carry over to the next. An item whose form had been deleted caused a fatal error instead of asking to be reconfigured.
Ordering again with the "resubmit" setting rejected valid items (list fields, email confirmation, decimal-comma numbers), could fatal on list fields with columns or a deleted form, ran the form's feeds from the second item on, lost the customer's single-file uploads and added a broken link to multi-file uploads. The order's own values and files are now carried into the cart.
Editing a cart item and saving it without changing anything doubled its quantity. The saved quantity now replaces the old one.
Choosing a variation on a product with a form filled the browser console with around 250 Gravity Forms deprecation warnings, and relied on a Gravity Forms function that is removed in Gravity Forms 4.0. The totals are now recalculated through Gravity Forms 3's products module.
Deactivating WooCommerce while this plugin was still active took the whole front end down with a critical error instead of a notice. WordPress checks a plugin's required plugins when it is activated, but not when one of those requirements is later switched off, so this plugin was left running with WooCommerce gone and called a WooCommerce function on every page. It now stops loading when WooCommerce is not present and starts again by itself once WooCommerce is back. This also covers a…
A product with a form attached could not be added to the cart by anything using WooCommerce's Store API, including saved wishlist rows and other extensions that re-add a previously configured item. The shopper was told only that the product "is not available for purchase". Adding a configurable product requires the form to have been filled in, and the check for that looked for a posted form - but a Store API request carries its data as JSON, so there was never a posted form to find and the…
Gravity Forms' anti-spam checks could reject an add to cart with "there was a problem with your submission" and no field marked as wrong, so nothing the shopper corrected made any difference. A form on a product is not submitted the way Gravity Forms expects - WooCommerce's add to cart form is used as the form and posted directly - and the honeypot, the source URL check, the submission speed check and reCAPTCHA v3 can all read that as bot activity. Those checks are now switched off for forms…
A required file upload field could report "there was a problem with your submission" even though the shopper had chosen a file, on themes that render their own add to cart form. A browser only sends the file itself when that form is marked enctype="multipart/form-data"; without it the field posts the file NAME as ordinary text and Gravity Forms sees the upload as missing. WooCommerce's own product templates set the attribute, so this only affected themes supplying their own markup - Divi's add…
On themes that add products to the cart via AJAX, a single click of Add to Cart could add a quantity of 2. Affected products used any attached form, including forms with no pricing fields. These themes (BeTheme is one, when WooCommerce's "Enable AJAX add to cart buttons on archives" setting is on) take over the Add to Cart button, serialise the whole form with FormData and post it to admin-ajax.php as a woocommerce_add_to_cart request. FormData omits submit buttons but includes hidden inputs…
Notas da versão 3.8.1: 2 novidades5 melhorias2 correçõesMostrarOcultar
Novidade
Attached form IDs are mirrored to indexed meta so products using a given form can be queried directly.
PHPUnit test suite.
Melhoria
Product settings are now defined in one place, replacing duplicated declarations across the save and read paths.
Cart item meta rows are now built by a single component, extracted from the cart class.
Stock quantity handling now shares the plugin's single conditional logic evaluator rather than a second copy of it.
Tested up to WordPress 7.1
A one-time background task runs after updating to index existing products.
Correção
Products could be added to the cart at $0.00 when a Gravity Forms Product field was shown or hidden by a third-party conditional logic add-on (such as MCG Advanced Conditional Logic). When rebuilding a cart line item we evaluate the form's conditional logic to decide which product fields count toward the price, but that evaluation did not run Gravity Forms' gform_rule_pre_evaluation filter. Add-ons that express their rules through that filter had them left unprocessed, so a product field that…
Conditional logic rules using "greater than" or "less than" against a currency-formatted value were compared as text instead of as numbers, so a rule such as "greater than 1000" did not match a value of 1,234.00. Numeric comparisons now normalise the value first, matching Gravity Forms.
Versão 3.7.12
Notas da versão 3.7.12: 1 melhoria2 correçõesMostrarOcultar
Melhoria
Tested up to WooCommerce 11.0
Correção
On Gravity Forms 3.0, the product subtotal and total stopped displaying on the product page for forms that do not contain a Gravity Forms "Total" field. Gravity Forms 3.0 moved price calculation into a new module that only recalculates, and fires the gform_product_total filter our display relies on, when the form contains a form-specific total field. Forms built without a Total field (relying on our subtotal/total display) therefore showed blank prices, even though the correct price was still…
A conflict with third-party Gravity Forms add-ons (such as GP Nested Forms) that could cause a fatal error (ArgumentCountError) when adding a product to the cart. While building the cart and order data we re-fire Gravity Forms' gform_pre_render filter, but were passing only the form object and not the additional arguments (ajax flag and field values) that Gravity Forms core supplies. Callbacks written to core's documented signature then received too few arguments. We now match core's signature…
Notas da versão 3.7.11: 1 melhoria1 correçãoMostrarOcultar
Melhoria
Requires at least WordPress 6.5 (required for the "Requires Plugins" dependency header).
Correção
A false "Gravity Forms Not Found" admin notice appeared after updating to Gravity Forms 3.0, even though Gravity Forms was installed and working. Our admin check tested for the legacy RGForms class, which Gravity Forms 3.0 removed. We no longer perform our own runtime dependency detection, the plugin already declares WooCommerce and Gravity Forms via the WordPress "Requires Plugins" header, which WordPress 6.5+ enforces on activation. This removes the false notice and prevents this class of…
Cart quantity management (the "cart quantity field" feature) stopped working for products with "Sold individually" / "Limit purchases to 1 item per order" enabled. WooCommerce 10.7 added a cart check that force-resets any sold-individually product back to a quantity of 1 on every cart render, which clamped the quantity our feature had set from the form field (showing an incorrect total and a "You can only have 1 ... in your cart" notice). We now re-apply the form-driven quantity and price…
Dynamic price calculation stopped updating when selecting product options after 3.7.7 (priced option fields such as checkboxes could stay at $0.00). Deferring the frontend script in 3.7.7 caused it to load after Gravity Forms 2.9+ initializes its price-field recalculation, so option changes no longer recalculated the total. The script now loads in the header (non-deferred), as it did before 3.7.7. The original WordPress 6.3 enqueue notice remains resolved (the invalid argument is no longer…
wp_enqueue_script was called with a 'defer' key in the $args array, which has not been a recognized key since WordPress 6.3. This triggered a "called incorrectly" notice and left the scripts un-deferred. Switched to the supported 'strategy' => 'defer' argument.
Compatibility with Gravity Forms 2.9+. GF's submission module binds a guard to #gform_ that blocks any native form submit it doesn't recognize ("Unsupported submission flow detected"), which could prevent Add to Cart on some themes (e.g. Flatsome) depending on script load order. We now neutralize that guard for our add-to-cart submit using a capture-phase listener, independent of load order, without affecting other submit paths.
The frontend script and stylesheet cache-buster was not tied to the plugin version, so returning visitors could be served stale JS/CSS after an update. Asset versions are now derived from the plugin version automatically.
Versão 3.7.6
Notas da versão 3.7.6: 2 melhorias1 correçãoMostrarOcultar
Melhoria
Tested up to WordPress 7.0
Tested up to WooCommerce 10.8
Correção
The gform_wrapper div introduced in 3.7.1 was being injected around every product's add-to-cart form, including products without an associated Gravity form. This broke variation price replacement in themes such as Woodmart. The wrapper is now only emitted on products that actually have a Gravity form attached.
Notas da versão 3.7.4: 2 melhorias1 correçãoMostrarOcultar
Melhoria
Tested up to WordPress 6.9
Tested up to WooCommerce 10.6
Correção
Compatibility with Gravity Forms 2.9.29+. Updated calls to GFCommon::get_lead_field_display to pass the entry array as the third parameter instead of the currency string, resolving PHP warnings on cart, checkout, and order creation. Backward compatible with older Gravity Forms versions.
Notas da versão 3.6.9: 1 melhoria2 correçõesMostrarOcultar
Melhoria
WC and WP Compatibility Updates.
Correção
Correct incorrect translation domain.
Be defensive in getting gravity forms history from very old orders.
Versão 3.6.8
Notas da versão 3.6.8: 1 novidade5 melhoriasMostrarOcultar
Novidade
Include a specific Gravity Forms Product Addons for WooCommerce log file.
Melhoria
WC and WP Compatibility Updates.
Update script versions on the front end to force cache busting.
Change the name of the extension to Gravity Forms Product Add-Ons for WooCommerce to match WooCommerce naming guidelines.
Modify all log messages to a consistent format.
Force full product link when cart edit is enabled.
2024
10 versões
Versão 3.6.7
Notas da versão 3.6.7: 2 novidades2 melhoriasMostrarOcultar
Novidade
Add filter, woocommerce_gravityforms_order_entry, to allow filtering the entry which is created during the order process. This is useful for setting entry field values before we send notifications or process feeds.
Add specific integration with GP Nested Forms. This allows for the creation of entries for nested forms when a product is ordered.
Melhoria
WC and WP Compatibility Tags.
Add the wp_nonce_field back for gravity forms processing.
Versão 3.6.6
Notas da versão 3.6.6: 3 melhoriasMostrarOcultar
Melhoria
Handle the fix from 3.6.5 better. The data-formid attribute was not being added to the form element in all situations.
Bump script versions to force cache busting.
WC and WP Compatibility Tags.
Versão 3.6.5
Notas da versão 3.6.5: 3 correçõesMostrarOcultar
Correção
Fix issue with Gravity Forms 2.9.0. Needed to add a data-formid attribute to the WooCommerce form element.
Fix issue with logging custom woocommerce_gravityforms_create_entries_on_specific_statuses filter.
Fix issue with missing form during reorder validation.
Versão 3.6.4
Notas da versão 3.6.4: 2 melhorias3 correçõesMostrarOcultar
Melhoria
WP and WC Compatibility Tags.
Remove the noonce generation when we render the product form.
Correção
Fix problem where add to cart validation would generate a warning on products with no form attached.
Fix issue with reordering a product with a list field that uses multiple columns.
Fix issue with WooCommerce Quick View Pro
Versão 3.6.3
Notas da versão 3.6.3: 2 melhorias2 correçõesMostrarOcultar
Melhoria
Respect the woocommerce_gforms_use_label_as_value setting for fields that do not have entry inputs.
Better handling for Limit purchases to 1 item per order. Filter the cart_id to remove data that changes or could change between form submissions, but is not related to the actual data of the form.
Correção
Fix issue with re-ordering products with file upload fields and required fields.
Fix issue where variable products could not be added to a Wishlist properly.
Versão 3.6.2
Notas da versão 3.6.2: 2 melhoriasMostrarOcultar
Melhoria
Update the display for checkbox type fields (regular and product options) to display better in checkout blocks.
Update package dependencies and include a version check script.
Versão 3.6.1
Notas da versão 3.6.1: 1 melhoria2 correçõesMostrarOcultar
Melhoria
WC and WP Compatibility Tags.
Correção
Fix issue with the mutation observer causing an infinate loop on some sites where gform is not available.
Only enqueue the admin scripts on a Gravity Forms admin page.
Versão 3.6.0
Notas da versão 3.6.0: 4 novidades1 melhoriaMostrarOcultar
Novidade
Integration with WooCommerce Bookings. The integration is basic, but allows for booking product costs to be correctly displayed in the totals section on the product page.
Updated styles to modernize and cleanup the look of the totals section.
Include custom merge tags for WooCommerce order and order item data.: {wc_order:order_id} - The WooCommerce order ID.; {wc_order:order_number} - The WooCommerce order number.; {wc_order:customer_id} - The WooCommerce order customer ID.; {wc_order:customer_email} - The WooCommerce order date.; {wc_order:billing_email} - The WooCommerce order billing email.; {wc_order:[ORDER_PROPERTY]} - Any other WooCommerce order property.
New Include custom merge tags for WooCommerce product information.: {wc_product:product_id} - The WooCommerce product ID.; {wc_product:product_sku} - The WooCommerce product SKU.; {wc_product:product_name} - The WooCommerce product name.; {wc_product:product_price} - The WooCommerce product price.; {wc_product:product_type} - The WooCommerce product type.; {wc_product:[PRODUCT_PROPERTY]} - Any other WooCommerce product property.
Melhoria
WC Compatibility Tags.
Versão 3.5.4
Notas da versão 3.5.4: 1 melhoria1 correçãoMostrarOcultar
Melhoria
WC Compatibility Tags.
Correção
Fix issue with the grand total not properly applying to the cart item.
Black FridayR$ 19,90por mês
Plano Budget no cartão, preço travado
na Black Friday
Lote 1 termina em00d00h00m
Próximo lote
R$ 24,90Ver a ofertaVer oferta