GravityMath Changelog

This release fixes errors and wrong results in Math Summary widgets, along with PHP warnings and miscounted empty values in View calculations.

🐛 Fixed

• 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 9,223,372,036,854,775,808 for a Minimum;
  • On PHP 8.3 and newer, values that are not numbers printed PHP warnings.
• 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).

💻 Developer Updates

• 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.

🔧 Updated

• Foundation to version 1.39.1.

This release adds live totals for DataTables Views, fixes a page crash on PHP 8, and resolves incorrect totals for several field types, currencies, and decimal formats.

🚀 Added

• [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.

🐛 Fixed

• 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 multiple inputs) counted each checked choice instead of each entry;
  • With scope="form", Consent field totals included the consent text and form revision saved with the entry;
  • In Views, totals of scored Survey (Likert) fields with multiple rows showed 0, both for the whole field and for each row.
• 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 sites with a custom currency whose symbol contains "/" (such as "S/" for the Peruvian sol, added with the gform_currencies filter);
  • Formulas were empty when a currency symbol starting with a capital letter (such as "R$", "CHF", "HK$", or "Kč") appeared anywhere but at the start, such as a Calculation field adding two Product prices on a site using the Brazilian real;
  • Formulas misread prices in currencies that format numbers differently from the site's language (on an English site, "R$ 2,50" was read as 250 and "1.234,56 €" as 1.23456);
  • Calculation fields read prices with a dot for thousands and a comma for decimals as whole numbers, such as "R$ 1.234,56" as 123456;
  • With scope="entry" and an entry ID, prices were read in the site's current currency instead of the currency the entry was saved in.
• 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 newer);
  • In Preloaded (Client-side) tables, Math Summary widgets set to "Entries shown on the page" kept showing the first page's results after paging, sorting, or searching;
  • A View placed below a Preloaded (Client-side) DataTables View calculated its View (Visible) footer results from the wrong entries;
  • In Preloaded (Client-side) tables, a PHP warning appeared on every page load when a column's footer calculation had no saved Decimals setting;
  • With two DataTables Views on the same page, each with a Math Summary widget, one table's results could appear in the other View's widget;
  • With two DataTables Views on the same page, one View's Calculation Row Position setting applied to both tables;
  • In tables set to "Hide View data until search is performed", Math Summary widgets showing all View entries sent their totals to the browser before any search was made.

💻 Developer Updates

• 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 (default: 1000, or the largest option in the View's rows-per-page menu if higher).

🔧 Updated

• Foundation to version 1.39.0.

This release improves date calculations, fixes several fatal errors and incorrect totals, corrects number formatting in languages such as German and French, and keeps personal information out of the GravityKit log; we recommend updating.

✨ Improved

• :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}.

🔒 Security

• 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).

🐛 Fixed

• 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 {Approved:is_approved:count}, showed 0;
  • Totals of a Product field without an input ID, such as {Product:5}, showed 0, or added prices and quantities when using a filter, instead of totaling the price as Gravity Forms calculations do;
  • Two totals for different inputs of the same field on one page, such as a Product's price and quantity, both showed the first one's total.
• 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 without a value were dropped;
  • Averages did not count entries without a value as the default in every scope, so scope="form" and scope="view" could give different averages.
• 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 could show 2.47 instead of 2,469.
• 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.

🔧 Updated

• Foundation to version 1.38.0.

This release fixes a fatal error on Views that join forms and resolves many issues with filters, including date, number, and multi-input field comparisons.

🐛 Fixed

• 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.

🔧 Updated

• Foundation to version 1.36.0.

This update restores a missing styling option for table-based Views on GravityView 3.0 and newer.

🐛 Fixed

• The Calculation Row Background setting was missing from the Multiple Entries settings of Table and DataTables Views on GravityView 3.0 and newer.

🔧 Updated

• Foundation to version 1.35.0.

This update fixes a database error when counting Multi Select choices.

Note: GravityMath now requires WordPress 6.5 or newer.

🐛 Fixed

• Database error when counting Multi Select choices individually with a filter and empty values included.

🔧 Updated

• Foundation to version 1.33.0.

This release shows choice labels instead of stored values when the Math Summary groups by a choice field, and fixes zero-value groups being dropped and translation notices in WordPress 6.7 and newer.

✨ Improved

• 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.

🐛 Fixed

• 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.

💻 Developer Updates

• Now uses the current GravityView hooks instead of ones deprecated in GravityView 2.55.

🔧 Updated

• Foundation to version 1.30.0.

This release includes internal component updates and bug fixes for improved stability and compatibility.

🔧 Updated

• Foundation to version 1.21.0.

This release fixes a fatal error in the GravityMath summary shortcode and block, and corrects how integer values with thousands separators are handled in the GravityView Calculation field.

🐛 Fixed

• A fatal error occurred when using the [gravitymath action="summary"] shortcode or gk-gravitymath/summary block without GravityView active.
• Integer values with a thousands separator (e.g., 1,123) in the GravityView Calculation field were misread as decimals.

🔧 Updated

• Foundation to version 1.16.1.

• Fixes fatal error on activation introduced in 2.10.2.

This release fixes filtered calculations returning incorrect results on sites with many form entries.

🐛 Fixed

• Filtered scope="form" calculations in the [gravitymath] shortcode and GravityView table footer now return correct results on forms with a large number of entries.

🔧 Updated

• Foundation to version 1.13.0.

This update fixes merge tags not working in [gravitymath] shortcode attributes inside GravityView Custom Content fields.

🐛 Fixed

• Merge tags in [gravitymath] shortcode attributes (e.g., filter) are now correctly replaced when used inside a GravityView Custom Content field.

🔧 Updated

• Foundation to version 1.9.0.

This release adds alphabetical sorting of data sources (form or View) in the GravityMath Summary block and fixes issues affecting the [gravitymath] shortcode.

✨ Improved

• Forms and Views are now sorted alphabetically in the GravityMath Summary block source selection dropdown.

🐛 Fixed

• The [gravitymath] shortcode now respects the scope and id attributes when used inside GravityView Views (e.g., Custom Content field).
• The filter attribute now correctly restricts summary results when using action="summary" in the [gravitymath] shortcode.

🔧 Updated

• Foundation to version 1.7.2.

This release resolves a fatal shortcode error and fixes multiple issues affecting currency formatting and calculations.

🐛 Fixed

• 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.

🔧 Updated

• Foundation to version 1.6.2.

This update fixes calculation issues involving currency-formatted fields.

🐛 Fixed

• Calculation field not working with currency-formatted Number fields and Product (price) fields.

This release introduces a new Calculation field for GravityView, removing the need to use the [gravitymath] shortcode inside Custom Content fields. Also fixes some minor bugs.

🚀 Added

• 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.

🐛 Fixed

• 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.

🔧 Updated

• Foundation to version 1.6.0.

This release adds compatibility with the GravityView Dashboard Views plugin.

🚀 Added

• Compatibility with the GravityView Dashboard Views extension.

This release adds dynamic Math Summary widget updates in GravityView’s DataTables layout, improves Date field filter handling in the [gravitymath] shortcode, and resolves footer calculation inaccuracies and a PHP notice in WordPress 6.8.

🚀 Added

• Support for GravityView's DataTables layout, enabling dynamic Math Summary widget updates during table filtering and sorting.

✨ Improved

• Date field filters in the [gravitymath] shortcode now accept field's display format values instead of requiring yyyy-mm-dd format.

🐛 Fixed

• 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.

🔧 Updated

• Foundation to version 1.2.25.

💻 Developer Updates

• Added: gk/gravitymath/summary/entries filter to modify the entries object used for calculations.

This update fixes an issue with configuring multiple Math Summary widgets in a View.

🐛 Fixed

• Adding more than one Math Summary widget to a View caused the "Group By" selection in the widget settings to be empty.

🔧 Updated

• Foundation to version 1.2.22.

This release adds support for Hidden fields in summary reports and addresses a non-critical PHP notice in WordPress 6.7 and newer.

🚀 Added

• Support for Hidden fields in summary reports.

🐛 Fixed

• PHP notice in WordPress 6.7 caused by initializing product translations too early.

🔧 Updated

• Foundation to version 1.2.21.

This release resolves issues with displaying currency-formatted fields in summary reports and fixes footer calculations not working in embedded Views.

🐛 Fixed

• 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.

🔧 Updated

• Foundation to version 1.2.20.

This release adds support for additional fields in summaries, addresses various issues, and updates internal components.

🚀 Added

• Support for Checkboxes and Radio Buttons fields in summaries.

🐛 Fixed

• 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.

🔧 Updated

• Foundation to version 1.2.19.

This hotfix release addresses a fatal error that can occur when creating a new View.

🐛 Fixed

• Fatal error when creating a new View under certain conditions.

This release introduces new tools for creating summary reports from your form data, enabling you to perform calculations across entries for deeper insights. It also includes minor fixes and security improvements. Read the announcement.

🚀 Added

• 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.

🐛 Fixed

• PHP 8.2 deprecation notice.

🔐 Security

• The [gravitymath] shortcode now requires a secret attribute when the scope is set to view and the View has Enhanced Security enabled.

🔧 Updated

• Foundation and TrustedLogin to versions 1.2.18 and 1.9.0, respectively.

💻 Developer Updates

• Added: gk/gravitymath/summary/data filter to modify the calculation data before rendering the summary table.
• Added: gk/gravitymath/summary/template filter to modify the template used to display the summary table.
• Added: gk/gravitymath/summary/headers filter to modify the table headers before rendering the summary table.

This release fixes a bug in the [gravitymath] shortcode's math calculations and updates the Foundation framework to improve support for sites that use object caching plugins.

🐛 Fixed

• An issue with math calculations in the [gravitymath] shortcode not functioning correctly unless scoped to a specific form or View.

🔧 Updated

• 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.

This release introduces new functionality for multi-select fields and resolves several issues related to footer calculations. It also features an updated version of Foundation that offers performance improvements and enhanced translation management.

🚀 Added

• Ability to calculate individual selected or unselected choices of a multi-select field.
• New option to position the footer calculation row either above or below the table's footer row.

🐛 Fixed

• 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".

🔧 Updated

Foundation to version 1.2.6
- Improved performance.
- Enhanced the loading and caching of plugin translations.
- All translations are now loaded from the wp-content/languages/plugins/<site ID> directory.
- Added support for installing plugin translations via WP-CLI (WordPress Command Line Interface).
- 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.

• Improved: Support for RTL languages
• Updated: Foundation to version 1.2.2

• Updated: Foundation to version 1.1.1

• Fixed: Incorrect calculation results for Survey fields (Likert type) with multiple rows that use score values
• Fixed: Calculation for Product fields with "user-defined price" not working when using the "filter" parameter in the [gravitymath] shortcode
• Fixed: Incompatibility with some plugins/themes that use Laravel components
• Updated: Foundation to version 1.0.12

Developer Updates:

• Added: 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
• Added: gk/gravitymath/table-footer-calculation/supported-fields-schema filter to modify the list of View fields that support table footer calculations

Note: GravityMath now requires PHP 7.2 or newer

• Updated: Foundation to version 1.0.9

• Fixed: Changing View settings or filters would not affect cached calculations
• Fixed: Calculations would be cached for Views connected to the same form
• Fixed: Pricing field calculations may not be accurate for values over 999 when using view and visible scopes

• Updated: Foundation to version 1.0.8

• Added: 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
• Fixed: Multiple filters, separated by & in the shortcode filter attribute, were not working correctly
• 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
• Fixed: Fatal error on some hosts due to a conflict with one of the plugin dependencies (psr/log)
• Fixed: PHP 8.1 notices

Developer Updates:

• Added: gk/gravitymath/use_db_cache filter to modify whether or not to use the database cache if GravityView is enabled. Default is true.

• Fixed: Count operation not working for multiple input fields (e.g., First Name [1.3])
• Fixed: Multiple PHP 8.x warnings
• Fixed: Fatal error on some hosts that use weak security keys and salts

• Fixed: It was not possible to remove an expired license key

• Fixed: "Undefined index" PHP notice
• Fixed: Product quantity footer calculation was being formatted as currency
• Fixed: Footer calculations were added in the Single Entry layout

• Fixed: Fatal error when loading plugin translations
• Fixed: Slow loading times on some hosts
• Fixed: Plugin failing to install on some hosts

• Fixed: Plugin was not appearing in the "Add-Ons" section of the Gravity Forms System Status page

• Fixed: Potential error when the plugin tries to log an unsuccessful operation

• Fixed: Error when trying to activate license keys

• Added: New WordPress admin menu where you can now centrally manage all your GravityKit product licenses and settings (learn more about the new GravityKit menu)
  • Go to the WordPress sidebar and check out the GravityKit menu!
  • We have automatically migrated your existing GravityMath license, which was previously entered in the Gravity Forms settings page
  • Request support using the "Grant Support Access" menu item
• Added: A new [gravitymath] shortcode—it works exactly the same as [gv_math], but it's named properly
• Fixed: PHP 8 warnings

• GravityView (the company) is now GravityKit and this plugin is now called GravityMath!
• Added: Support for product field with "Radio Buttons", "Drop Down" and "User Defined Price" field types

Developer Updates:

IMPORTANT: GravityView_Math_* classes were renamed to GravityMath_* and future versions will see gravityview/math/* hooks renamed to gk/gravitymath/*

• Fixed: "Trying to get property of non-object" notice when displaying a View with footer calculations
• Fixed: Incorrect calculation of the average Quiz Score
• Added: Option to calculate a sum of the Quiz Score

• Fixed: Filters using CONTAINS or NOTCONTAINS operators would not work
• Fixed: Filters would not work with multi-input fields unless the exact input is specified

• Fixed: Fatal error if performing calculations using Gravity Forms data, using the shortcode's filter attribute, and GravityView is not installed
• Fixed: Filter conditions using fields with multiple input did not work

• Fixed: Incorrect formatting of calculation results with certain locales
• Added: Option to specify the number of decimal places for footer calculations

• Fixed: PHP fatal error when the plugin is used without GravityView
• Added: Footer calculations for Custom Content fields

• Added: Easily add footer calculations to your GravityView Table and DataTables layouts! Learn how to add calculations.
  • Effortlessly calculate field values
  • Quiz: # Passed, # Failed, % Passed, % Failed, Average Score
  • High, low, average, sum, checked
  • Count of checked and unchecked checkboxes, radio inputs, consent fields
  • Time duration: Fastest, slowest, average time
• Added: Perform duration calculations, great for races and time sheets! See a video for setting up duration calculations.
• Added: Filter support for scope="visible". Read more about filters.
• Added: An {entry_count} Merge Tag you can use inside math formula as well as throughout Gravity Forms and GravityView! Read about the {entry_count} Merge Tag
• Improved: Execution time when a Math filter is used on large data sets
• Fixed: Incorrect results returned by min/max/avg/sum operations
• Fixed: Calculations on non-numeric fields (e.g., product price) would not work in View widget areas
• Fixed: Only using one page of results were used when calculating scope="view"
• Logging improvements!
  • New: Not sure why your Math formula isn't working, but you don't want to modify the shortcode? Administrators can now debug Math formulae from the front-end by adding ?gv_math_debug=true to the URL.
  • Added: Better debugging information is now shown, including the contents of the formula before and after it was processed.
  • Improved: Notices are now grouped for each shortcode, making it easy to debug.
  • Fixed: "Additional info" shown when debugging results not displaying when clicked.
  • Fixed: Math by GravityView wasn't showing in the Gravity Forms "Logging" screen.
  • Fixed: Display user notices only when notices shortcode attribute is set.

• Fixed: If using scope=form as well as a filter, only the first 20 entries in the form were used in calculations

• Fixed: Shortcode not working when used inside GravityView DataTables layouts
• Updated: French translation

• Fixed: The [gvmath] shortcode not working properly inside GravityView [gvlogic] shortcodes
• Fixed: Potential errors when editing content in Gutenberg editor
• Fixed: Potential error when using Math while running Gravity Forms < 2.3 and GravityView < 2.5
• Fixed: Properly handles dates passed via Merge Tags
• Added: Support for Gravity Forms Merge Tags in the filter attribute (when using scope="form")

Developer Updates:

• Added: gravityview/math/debug filter to modify whether debugging is on or off. Return false to disable debugging. Note: Viewing debugging requires edit_others_posts capability.

• The plugin now requires PHP 7.1
• Added: Filtering on form and view scopes. This will filter the entries in the scope by the specified values. Read more about filtering.
• Fixed: SQRT_PI, SQRT_{Number} functionality
• Added: Russian Translation (thanks, Viktor S) and Ukrainian translation (thanks, Dariusz Zielonka!)
• Updated: Chinese translation (thanks, Edi Weigh!)

• Fixed: Aggregate form data not calculating with Gravity Forms 2.3
• Fixed: .mo translation files weren't being generated
• Updated: Dutch, Turkish, and Spanish translations (thanks, jplobaton, SilverXp, and suhakaralar!)

• Fixed: Compatibility with Gravity Forms 2.3
• Updated: Dutch and Turkish translations

• Fixed: Don't link to entry in debug mode if the entry doesn't exist 👻
• Fixed: Incorrect argument passed to Gravity Forms Add-On registration function
• Fixed: Compatibility issue with the Gravity Forms Utility plugin - thanks, Naomi C Bush!

• Fixed PHP error when there are no values to calculate
• Updated German translation (Thank you, Hubert Test!)

• Fix potential error blocking activation

• Launch!