Descripción
Gravity Forms Product Add-ons conecta formularios de Gravity Forms con los productos de WooCommerce, permitiendo vender productos personalizables con campos avanzados en el proceso de pago. Los valores elegidos por el cliente en los campos del formulario se calculan automáticamente y se suman al precio final del producto, generando pedidos completos con todas las opciones seleccionadas registradas en los datos de la compra.
Principales características de Gravity Forms Product Add-ons
- Vinculación del formulario con el producto
Asocia cualquier formulario de Gravity Forms con un producto WooCommerce en la pantalla de edición. - Cálculo dinámico del precio
Recalcula el valor del producto en tiempo real a medida que el cliente completa opciones y cantidades. - Campos condicionales en el producto
Muestra u oculta campos según las elecciones anteriores realizadas dentro del mismo formulario. - Datos guardados en el pedido
Guarda las respuestas del formulario junto a la línea del artículo dentro del pedido de WooCommerce. - Compatibilidad con tipos de WooCommerce
Funciona con productos simples, variables y virtuales sin alterar el flujo estándar del carrito.
Beneficios de Gravity Forms Product Add-ons
- Catálogo configurable sin código
Permite ofrecer productos a medida mediante la interfaz visual de Gravity Forms. - Menos pedidos con errores
Las validaciones nativas de Gravity Forms reducen los datos incompletos antes de llegar al proceso de pago. - Mayor valor promedio de compra
Las opciones adicionales de pago incentivan las mejoras durante la elección del producto. - Operación centralizada
Todas las personalizaciones quedan visibles dentro del pedido, facilitando la producción y la entrega.
¿Para quién está indicado Gravity Forms Product Add-ons?
- Quienes venden productos por encargo, como camisetas estampadas, tazas personalizadas, joyas grabadas o pasteles decorados.
- Quienes ya usan Gravity Forms en el sitio y necesitan transformar formularios de presupuesto en compras directas en WooCommerce.
- Quienes ofrecen servicios con opciones adicionales de pago, como paquetes fotográficos, clases particulares o planes de consultoría.
Cómo descargar Gravity Forms Product Add-ons
Gravity Forms Product Add-ons está disponible para descargar aquí en Ultrapack. Después de descargar el archivo .zip, instálelo en Plugins > Añadir nuevo > Subir plugin, seleccione el archivo y actívelo. Con WooCommerce y Gravity Forms activos, la pestaña de configuración del addon aparece en la pantalla de edición de cada producto.
Dirigida a tiendas que necesitan ir más allá del producto fijo, la extensión Gravity Forms Product Add-ons aprovecha toda la lógica condicional y los tipos de campo de Gravity Forms dentro del flujo de compra de WooCommerce. Para quienes trabajan con personalización, opciones adicionales de pago o instrucciones detalladas antes de la producción, es el vínculo que une la recopilación de datos y el cobro en una sola etapa.
Preguntas frecuentes
¿El plugin WooCommerce Gravity Forms Product Add-ons es GPL?
Sí. WooCommerce Gravity Forms Product Add-ons se distribuye bajo la licencia GPL (GNU General Public License). Puedes usarlo, modificarlo y redistribuirlo legalmente en todos los sitios que quieras.
¿Puedo usar el plugin WooCommerce Gravity Forms Product Add-ons en más de un sitio?
Sí. Puedes instalar WooCommerce Gravity Forms Product Add-ons en todos los sitios que quieras. Solo las actualizaciones automáticas con Ultrapack Auto Updater tienen límite: de 3 a 80 sitios, según el plan.
¿Cuánto cuesta el plugin WooCommerce Gravity Forms Product Add-ons en Ultrapack?
WooCommerce Gravity Forms Product Add-ons cuesta US$ 2,99 en la compra individual, y también está incluido en los planes de suscripción desde US$12/mes (VIP I).
¿El plugin WooCommerce Gravity Forms Product Add-ons incluye actualizaciones?
Sí. La versión actual de WooCommerce Gravity Forms Product Add-ons es la 3.8.5, publicada en Ultrapack el 01/10/2026. Los suscriptores actualizan directamente desde el panel de WordPress con UAU (Ultrapack Auto Updater).
¿Es seguro descargar e instalar el plugin WooCommerce Gravity Forms Product Add-ons en mi WordPress?
Sí. Cada versión de WooCommerce Gravity Forms Product Add-ons pasa por un análisis de malware (ClamAV y reglas YARA, en UltraHub) antes de publicarse.
¿Cuáles son los requisitos del plugin WooCommerce Gravity Forms Product Add-ons?
Requiere WordPress 6.5 o superior. Probado hasta WordPress 7.1.
Qué cambió en esta versión
Versión 3.8.5 2026.09.27
- Update: Tested up to WooCommerce 11.1
- Fix: 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.
- Fix: 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.
- Fix: 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.
- Fix: Editing a cart item and saving it without changing anything doubled its quantity. The saved quantity now replaces the old one.
- Fix: 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.
Versión 3.8.4 2026.09.03
- Fix: 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 item was refused. Where the request carries the entry that was already filled in and validated when the item was saved, that entry is now checked instead: it must belong to the form the product actually offers, and that form must still exist, still be active and not be in the trash. A genuinely unconfigured product carries no entry and is still refused, exactly as before.
- Fix: 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 attached to a product; forms used anywhere else keep their protection. The plugin has claimed to do this since the honeypot was introduced, but the setting it changed was never the one Gravity Forms reads.
- Fix: 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 to cart module is the reported case. The form is now given the attribute whenever it contains a file field. Multi-file upload fields were never affected, because they upload separately and do not depend on the enclosing form, which is why switching a field off multi-file mode appeared to cause the problem.
Versión 3.8.3 2026.08.29
- Update: WordPress 6.5 is now the minimum supported version
Versión 3.8.2 2026.08.25
- Fix: 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, so the hidden "add-to-cart" field we add to the form travelled with that request - and WooCommerce then added the product twice from the one request, once through its form handler (which runs on any request carrying an add-to-cart value) and once through its AJAX handler. WooCommerce's own templates already carry that value on every purchasable product type - on the submit button for simple products, and on WooCommerce's own hidden input for variable and grouped ones - so our copy was redundant on a normal product page. It is only needed on the pages of a multi-page form, where we remove the submit button and move between pages by submitting the form in the background. It is now emitted only in that case, so the AJAX request no longer triggers the second add.
Versión 3.8.1 2026.08.22
- Fix: 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 was actually visible was treated as hidden and dropped from the price calculation, leaving the line item at $0.00. Conditional logic is now evaluated through Gravity Forms' documented extension points (gform_rule_pre_evaluation and gform_rule_source_value), so these add-ons behave the same way on the product page and in the cart.
- Fix: 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.
- Refactor: product settings are now defined in one place, replacing duplicated declarations across the save and read paths.
- Refactor: cart item meta rows are now built by a single component, extracted from the cart class.
- Refactor: stock quantity handling now shares the plugin's single conditional logic evaluator rather than a second copy of it.
- Add: attached form IDs are mirrored to indexed meta so products using a given form can be queried directly.
- Add: PHPUnit test suite.
- Update: Tested up to WordPress 7.1
- Note: a one-time background task runs after updating to index existing products.
Notas de versión publicadas por el desarrollador.
Cómo instalar
Actualización automática: este ítem se actualiza con el Ultrapack Auto Updater. Con él instalado, la versión nueva aparece en tu panel como cualquier otra actualización de WordPress (cómo configurarlo).
- Descarga el archivo
woocommerce-gravityforms-product-addons.zip. - En el panel de WordPress, ve a Plugins > Añadir nuevo > Subir plugin.
- Selecciona el archivo
woocommerce-gravityforms-product-addons.zipy haz clic en Instalar ahora. - Haz clic en Activar.
Requisitos: Requiere WordPress 6.5 o superior. Probado hasta WordPress 7.1.
¿Te trabaste en algún paso? Abre un ticket diciendo en cuál te detuviste.

UAU Ready