O que mudou em cada versão, da mais recente para a mais antiga. As notas são as publicadas pelo desenvolvedor, no idioma original.
Mais recente 2.14.1 · 5 nov 2026
58 versões
Desde maio 2017
2026
13 versões
Versão 2.14.1
Mais recente
Notas da versão 2.14.1: 8 melhoriasMostrarOcultar
Melhoria
On PHP 8.3 and newer, View totals and footer calculations could print the warning "array_sum: Addition is not supported on type string" once for each entry with an empty value, such as a Number field left blank.
In Views, averages, minimums, and maximums of some fields other than Number fields, such as Radio Buttons, Option, and scored Survey fields, counted entries without a value as 0 and ignored a numeric default_value, so results differed from scope="form".
Issues with Math Summary widgets set to "Entries shown on the page": The Minimum or Maximum of a Checkbox field with more than one choice checked, of an Option field, or of a field with text choices could stop the page from loading;; Checkbox fields counted only the first checked choice;; Option field sums showed 0, and minimums or maximums could show 0 or 9,223,372,036,854,775,808;; Averages counted entries without a value, and values of 0 were left out;; Groups without any value showed 0, or…
Math Summary widgets set to "All View entries" and GravityMath Summary blocks with a Top display, such as Top 3, could show fewer groups when a group had no value in the field.
A Math Summary widget or GravityMath Summary block whose Group By field no longer exists printed a PHP notice or warning.
In Preloaded (Client-side) DataTables Views, View (Visible) footer averages of price fields counted entries without a price as 0 (requires DataTables 3.15.0 or newer).
The gravityview/math/aggregate_data/modify_field_value filter now receives an empty string instead of 0 for entries without a value in some fields other than Number fields, such as Radio Buttons, Option, and scored Survey fields.
Notas da versão 2.14.0: 1 novidade7 melhoriasMostrarOcultar
Novidade
Added filters for live scope="visible" totals in DataTables Views: gk/gravitymath/datatables/visible/live to turn them off (default: true);; gk/gravitymath/datatables/visible/max-tokens to set how many totals a table updates on each draw (default: 20);; gk/gravitymath/datatables/visible/hidden-fields to let totals read fields the table doesn't show as columns (default: false);; gk/gravitymath/datatables/visible/max-rows to set how many rows a Preloaded (Client-side) table's totals cover…
Melhoria
[gravitymath scope="visible"] totals in the Custom Content widgets of DataTables Views now add up the rows on screen and update as visitors search, sort, or page through the table (requires DataTables 3.15.0 or newer); to keep hidden values private, this does not apply to totals of fields the table doesn't show as columns.
On PHP 8, formulas that could not be calculated (such as max(1,2) or max(5)) crashed the whole page instead of returning an empty result.
A file in the bundled math library, now removed, failed PHP compatibility checks on PHP 8.1.2.
Incorrect totals for several field types: In Views, including Ajax (Server-side) DataTables Views, totals and footer calculations of Product (Single, Hidden, and Calculation), Option, Checkbox, and Consent fields showed 0 when the merge tag had no input ID, such as {Widget:1:sum} (Product fields now add up their prices, as scope="form" does);; With scope="form", Option field totals showed 0;; With scope="form", averages, minimums, maximums, and counts of Checkbox fields (and other fields with…
Incorrect results with currencies and decimal numbers: On sites in languages that use a comma for decimals (such as German) or with a currency that does (such as the euro), totals of prices with cents and of decimal choice values were 10 or 100 times too large, and scope="form" totals of decimal choice values lost their decimals;; View totals of Shipping and Option fields included digits from choice labels, such as the 2 in "Zone 2";; All formulas were empty and footer totals showed 0.00 on…
Issues in DataTables Views: In Ajax (Server-side) tables, the Math Summary widget stayed empty with DataTables 3.14.0 or newer;; In Ajax (Server-side) tables with footer calculations, footer Field Filters did not appear, the footer label of a pinned column did not stay pinned, and hiding a column with the Columns button left its footer cells visible;; In Preloaded (Client-side) tables, footer calculations did not update after a search with the Search Bar widget (requires DataTables 3.15.0 or…
Foundation to version 1.39.0.
Versão 2.13.0
Notas da versão 2.13.0: 12 melhoriasMostrarOcultar
Melhoria
Timestamp merge tags in calculations now return the actual time regardless of the site's time zone, so date differences stay correct across daylight saving changes and against {today:timestamp} or {now:timestamp}.
Calculation messages written to the GravityKit log now identify entries, forms, and fields by ID only, instead of including entry values, visitor details such as IP addresses, filled-in formulas, filters, default values, or error text (the debug report on the page still shows these to users allowed to see it).
On PHP 8, [gravitymath scope="entry"] caused a fatal error when the formula used a merge tag with a modifier, such as {date_updated:timestamp} or {created_by:ID}.
[gravitymath scope="entry"] caused a fatal error when its id pointed to an entry that did not exist, such as a deleted one (it now shows nothing, and the debug report names the missing entry).
The bundled math library included command-line tools that failed PHP 8 compatibility checks and caused a fatal error if loaded (they have been removed).
Issues with scope="form" totals: With GravityView active, totals with a relative date or merge tag in their filter, such as filter_date_created=today or filter_created_by={user:ID}, showed a cached result for up to a day, so they could show yesterday's total after midnight or another user's total;; Without a filter, totals of a Checkbox field (or another multi-input field given without an input ID), of one row of a multi-row Likert field, or of an entry meta key with an underscore, such as…
Issues with a numeric default_value: In scope="form" totals, it produced wrong numbers, such as 1 for a sum of 1,234.5, and was not applied to entries without a value;; With a filter, the default was subtracted, or added for entries the filter left out, and on forms with hundreds of entries the number of entries without a value was miscounted;; {Number:1:min} compared the default with the largest value instead of the smallest;; In scope="view" and scope="visible", values read before an entry…
In GravityView Custom Content fields, scope="form" and scope="entry" totals with a merge tag in their attributes, such as filter="filter_2={Team:2}" or id="{Other entry:3}", showed the row's own value instead of the total, and filter values containing & or +, such as R&D, matched nothing.
Issues with number formats in languages that use a comma for decimals or a dot for thousands, such as German or French: Calculation results and Math Summary values lost their decimals (1234.5 showed as 1.235), which also threw off anything calculated from a form total;; scope="entry" read decimal entry values as whole numbers, so 1000.25 was calculated as 100025;; With GravityView active on multilingual sites, form totals could appear in another language's number format, so {Number:1} * 2…
In PDFs from PDF for GravityView, GravityMath displayed raw code when an entry showed another View through the View field.
On PHP 8.4, calculations could show "Deprecated" notices when WordPress debugging was on.
Foundation to version 1.38.0.
Versão 2.12.3
Notas da versão 2.12.3: 8 melhoriasMostrarOcultar
Melhoria
Using scope="view" with a View that joins forms using the Multiple Forms extension caused a fatal error.
Filters with a form ID before the field (for example, filter_4:date_created) were ignored, so results included entries the filter should have excluded (in the visible scope, these filters excluded every entry instead).
Filters using lt or gt compared numbers as text, so 5 counted as greater than 10.
Issues with Date and Time field filters: With no date format saved, a value such as 09/15/2026 was read as 2026-15-09;; Partial values such as 2026 matched no entries;; Dates without leading zeros, such as 9/5/2026, were compared incorrectly;; Filters on Time fields, or on Date fields displayed as drop downs or text boxes, matched no entries.
Issues with filters on Checkbox, Name, and other multi-input fields without an input ID: Filters using isnot or notcontains included entries that had the value checked;; The Math Summary showed no results (for example, with filter_3=Red&op_3=contains).
Issues in the visible scope: Filters using lt, gt, or notcontains excluded every entry;; The debug report's "no entries" warnings showed the page title instead of naming the filter or View.
Issues on Views that merge forms with a union: Filters using is or contains on a Checkbox field left out the merged form's entries;; scope="view" and scope="visible" used the wrong fields from the merged form;; The Math Summary left out the merged form's entries.
The Math Summary now displays choice labels instead of stored values when grouping by a choice field, with a new "Use values for labels" setting (the use_values shortcode attribute) to restore the previous behavior.
The Math Summary group column is now escaped before output.
The Math Summary widget dropped groups with a stored value of "0" or a calculated result of 0 when set to "Entries shown on the page".
Editing a View triggered "Translation loading for the gravityforms domain was triggered too early" (_load_textdomain_just_in_time) notices in WordPress 6.7 and newer.
Now uses the current GravityView hooks instead of ones deprecated in GravityView 2.55.
Filtered scope="form" calculations in the [gravitymath] shortcode and GravityView table footer now return correct results on forms with a large number of entries.
Foundation to version 1.13.0.
Versão 2.10.1
Notas da versão 2.10.1: 2 melhoriasMostrarOcultar
Melhoria
Merge tags in [gravitymath] shortcode attributes (e.g., filter) are now correctly replaced when used inside a GravityView Custom Content field.
Fatal error when the [gravitymath] shortcode referenced a View ID that did not exist.
Inconsistent behavior between Number fields using the "Currency" format and Product fields.
Incorrect parsing of currency values when using the DataTables client-side rendering with comma-decimal currencies (e.g., DKK, EUR), where values like "47.000,00 kr." were treated as 47 instead of 47000.
Currency calculations now correctly use the currency stored with each entry rather than the WordPress locale, ensuring accuracy when site-wide currency settings change or when displaying entries with mixed currencies.
Notas da versão 2.9: 1 novidade4 melhoriasMostrarOcultar
Novidade
New Calculation field for GravityView that displays formula-based calculations with professional formatting. (Read about the Calculation field).: Removes the need to use the [gravitymath] shortcode inside Custom Content fields.; Supports number and currency formatting.; Includes customizable decimal places, thousands separators, and prefix/suffix options.
Melhoria
Math Summary blocks now properly validate View IDs before processing.
REST API endpoints for Math Summary now handle invalid View IDs gracefully with proper error messages.
Improved compatibility with GravityView Maps layout when rendering Math Summary blocks outside of GravityView post contexts.
Compatibility with the GravityView Dashboard Views extension.
Versão 2.8
Notas da versão 2.8: 1 novidade6 melhoriasMostrarOcultar
Novidade
Gk/gravitymath/summary/entries filter to modify the entries object used for calculations.
Melhoria
Support for GravityView's DataTables layout, enabling dynamic Math Summary widget updates during table filtering and sorting.
Date field filters in the [gravitymath] shortcode now accept field's display format values instead of requiring yyyy-mm-dd format.
Sum calculations for Number fields using comma decimal separators in locales with period thousands separators.
Incorrect footer calculations in GravityView's DataTables layout.
PHP notice in WordPress 6.8 related to early product translation initialization.
Foundation to version 1.2.25.
Versão 2.7.1
Notas da versão 2.7.1: 1 novidade1 melhoriaMostrarOcultar
Novidade
Adding more than one Math Summary widget to a View caused the "Group By" selection in the widget settings to be empty.
Melhoria
Foundation to version 1.2.22.
2024
7 versões
Versão 2.7
Notas da versão 2.7: 3 melhoriasMostrarOcultar
Melhoria
Support for Hidden fields in summary reports.
PHP notice in WordPress 6.7 caused by initializing product translations too early.
Foundation to version 1.2.21.
Versão 2.6.1
Notas da versão 2.6.1: 3 melhoriasMostrarOcultar
Melhoria
Error when displaying a Number field formatted as currency in summary reports.
Footer calculations not working when an embedded View is displayed in a Single Entry layout.
Foundation to version 1.2.20.
Versão 2.6
Notas da versão 2.6: 5 melhoriasMostrarOcultar
Melhoria
Support for Checkboxes and Radio Buttons fields in summaries.
Fatal error when creating a new View under certain conditions.
Summary blocks and shortcodes would break when GravityView is not active.
Shortcodes with visible or view scopes would not return results when filtering multi-input fields without providing input IDs.
Foundation to version 1.2.19.
Versão 2.5.1
Notas da versão 2.5.1: 1 melhoriaMostrarOcultar
Melhoria
Fatal error when creating a new View under certain conditions.
Versão 2.5
Notas da versão 2.5: 3 novidades3 melhorias1 reforço de segurançaMostrarOcultar
Novidade
Gk/gravitymath/summary/data filter to modify the calculation data before rendering the summary table.
Gk/gravitymath/summary/template filter to modify the template used to display the summary table.
Gk/gravitymath/summary/headers filter to modify the table headers before rendering the summary table.
Melhoria
Option to display calculation summaries using a block, shortcode, or widget.: Supports grouping entries by fields, performing mathematical operations (e.g., Count, Sum, Average), sorting and displaying top results.; The summaries can be shown for all View entries or only those displayed on the current page.
PHP 8.2 deprecation notice.
Foundation and TrustedLogin to versions 1.2.18 and 1.9.0, respectively.
Segurança
The [gravitymath] shortcode now requires a secret attribute when the scope is set to view and the View has Enhanced Security enabled.
Versão 2.4.1
Notas da versão 2.4.1: 2 melhoriasMostrarOcultar
Melhoria
An issue with math calculations in the [gravitymath] shortcode not functioning correctly unless scoped to a specific form or View.
Foundation was updated to version 1.2.7.: Improved the setting and retrieval of transients when using object cache plugins.; Fixed a JavaScript warning that appeared during the deactivation of license keys.
Versão 2.4.0
Notas da versão 2.4.0: 2 novidades7 melhorias3 correçõesMostrarOcultar
Novidade
New option to position the footer calculation row either above or below the table's footer row.
Added support for installing plugin translations via WP-CLI (WordPress Command Line Interface).
Melhoria
Ability to calculate individual selected or unselected choices of a multi-select field.
Survey field (Likert type) score not being calculated correctly.
Duration (text field with "hh:mm:ss" or "mm:ss" input mask) calculations not working correctly when scope is set to "form".
Counting unselected or unchecked radio/checkbox/select field inputs would return "0" when scope is set to "form".
Shipping field calculation producing incorrect results when scope is set to "form".
Improved performance.
Enhanced the loading and caching of plugin translations.: All translations are now loaded from the wp-content/languages/plugins/ directory.
Correção
Fixed an issue where deactivating a product on one site in a multisite environment caused this product's translations to be deleted across all sites.
Fixed PHP 8.2 deprecation warnings.
Fixed a PHP warning encountered when updating plugins from the WordPress Plugins page.
2023
6 versões
Versão 2.3.5
Notas da versão 2.3.5: 2 melhoriasMostrarOcultar
Melhoria
Support for RTL languages
Foundation to version 1.2.2
Versão 2.3.4
Notas da versão 2.3.4: 1 melhoriaMostrarOcultar
Melhoria
Foundation to version 1.1.1
Versão 2.3.3
Notas da versão 2.3.3: 2 novidades1 melhoria3 correçõesMostrarOcultar
Novidade
Gk/gravitymath/scope/form/transform-meta-value filter to modify the SQL statement used to transform the meta value for complex fields such as multi-row Survey (Likert) or Product with user-defined price
Gk/gravitymath/table-footer-calculation/supported-fields-schema filter to modify the list of View fields that support table footer calculations
Melhoria
Foundation to version 1.0.12
Correção
Incorrect calculation results for Survey fields (Likert type) with multiple rows that use score values
Calculation for Product fields with "user-defined price" not working when using the "filter" parameter in the [gravitymath] shortcode
Incompatibility with some plugins/themes that use Laravel components
Versão 2.3.2
Notas da versão 2.3.2: 2 melhoriasMostrarOcultar
Melhoria
GravityMath now requires PHP 7.2 or newer
Foundation to version 1.0.9
Versão 2.3.1
Notas da versão 2.3.1: 3 correçõesMostrarOcultar
Correção
Changing View settings or filters would not affect cached calculations
Calculations would be cached for Views connected to the same form
Pricing field calculations may not be accurate for values over 999 when using view and visible scopes
Versão 2.3
Notas da versão 2.3: 1 melhoriaMostrarOcultar
Melhoria
Foundation to version 1.0.8
2022
11 versões
Versão 2.2
Notas da versão 2.2: 2 novidades1 melhoria3 correçõesMostrarOcultar
Novidade
Support for nesting shortcodes! Perform calculations inside calcuations using multiple forms (read more about nested calculations): Added: [gravitymath2] and [gravitymath3] shortcodes for use inside a [gravitymath] shortcode
Gk/gravitymath/use_db_cache filter to modify whether or not to use the database cache if GravityView is enabled. Default is true.
Melhoria
Cache improvements: Improved cache speed by returning object cache before checking GravityView cache (if GravityView is active); Don't use cache when a form has been submitted on the page or if ?nocache, ?cache=0, or ?gform_debug are in the URL; Fixed cache showing the wrong value when using the :count modifier in certain cases
Correção
Multiple filters, separated by & in the shortcode filter attribute, were not working correctly
Fatal error on some hosts due to a conflict with one of the plugin dependencies (psr/log)
PHP 8.1 notices
Versão 2.1.4
Notas da versão 2.1.4: 3 correçõesMostrarOcultar
Correção
Count operation not working for multiple input fields (e.g., First Name [1.3])
Multiple PHP 8.x warnings
Fatal error on some hosts that use weak security keys and salts
Versão 2.1.3
Notas da versão 2.1.3: 1 correçãoMostrarOcultar
Correção
It was not possible to remove an expired license key
Versão 2.1.2
Notas da versão 2.1.2: 3 correçõesMostrarOcultar
Correção
"Undefined index" PHP notice
Product quantity footer calculation was being formatted as currency
Footer calculations were added in the Single Entry layout
Versão 2.1.1
Notas da versão 2.1.1: 3 correçõesMostrarOcultar
Correção
Fatal error when loading plugin translations
Slow loading times on some hosts
Plugin failing to install on some hosts
Versão 2.1.0.3
Notas da versão 2.1.0.3: 1 correçãoMostrarOcultar
Correção
Plugin was not appearing in the "Add-Ons" section of the Gravity Forms System Status page
Versão 2.1.0.2
Notas da versão 2.1.0.2: 1 correçãoMostrarOcultar
Correção
Potential error when the plugin tries to log an unsuccessful operation
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