Math by GravityView 2.12.0

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

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](https://www.gravitykit.com/foundation/) to version 1.16.1.

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](https://docs.gravitykit.com/article/957-client-side-processing) 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](https://www.gravitykit.com/foundation/) to version 1.6.2.

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

#### Added
* New Calculation field for GravityView that displays formula-based calculations with professional formatting.
- 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.

2.7.1

#### Added
* Support for Hidden fields in summary reports.

#### Fixed
* PHP notice in WordPress 6.7 caused by initializing product translations too early.

#### Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.2.21.

#### 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](https://www.gravitykit.com/foundation/) to version 1.2.20.

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