Published

Updated

Launch Log: GravityBoard voting, conditional logic upgrades, and HTTP Basic Auth support

This week's releases introduce card voting in GravityBoard, conditional logic improvements across the suite, and background-job support for sites behind HTTP Basic Authentication.

This week’s releases introduce card voting in GravityBoard, a broad set of conditional logic improvements across the suite, and background-job support for sites behind HTTP Basic Authentication. There are also targeted fixes for DataTables pagination, Maps search visibility, and joined-form conditional logic in the Advanced Filter Extension.

GravityBoard v1.4.0

This update to GravityBoard introduces Voting, letting your team or community decide what matters most on any board. Cards now support upvote and downvote buttons so users can signal priority, with optional per-user vote budgets (daily, weekly, monthly, yearly, or all-time) to pace participation. Voting can be scoped to specific lanes, so you can enable it in “Ideas” or “Under Review” while keeping “Done” read-only, and an upvote-only mode hides the downvote button for idea and feature-request boards where downvoting doesn’t belong.

New “Who Can Vote on Cards” and “Who Can See Who Voted” permission settings open voting to a broad audience while keeping voter identities visible only to admins or editors. Each card shows a weight badge when a user has stacked multiple votes, and the vote widget displays remaining budget so users can pace their support. An optional voters list surfaces who voted, with a “(You)” badge next to the current user.

Voting integrates directly with GravityView layouts. A new “Entry Voting” field renders the interactive vote widget in any layout, “Votes Count” shows a read-only sortable count, and a “Voted By” Advanced Filter targets entries the logged-in user has voted on, which is ideal for “My Voted Ideas” Views.

You can also set the default View sort by Votes Count ascending or descending, and vote counts stay in sync across multiple vote widgets on the same page. Two new notification merge tags let you include vote data and voter email addresses in any Gravity Forms notification:

  • {gravityboard_votes:count|average|total|up|down}
  • {gravityboard_voters:emails}

Watch a quick video to see voting in action

This release also improves error handling and conditional logic. The board now surfaces an error message when the REST API fails to load board data, instead of a silent blank screen. Conditional logic no longer treats empty field values as today’s date when using is on, is not on, is before, or is after filters, filters on deleted or missing forms no longer trigger errors, and admin-only filters (those suffixed :disabled_admin) work correctly when applied to multi-value fields. A regression that caused administrators to lose access to boards on sites relying on the gform_full_access capability has also been fixed.

Developer updates

  • Added the gk/gravityboard/permissions/admin-has-full-access filter to control whether administrators bypass all board permission checks. Read the documentation.

GravityCalendar v2.16.0

GravityCalendar gets the same round of conditional logic fixes shipping across the suite this week. Empty field values are no longer treated as today’s date in date-based comparisons (is on, is not on, is before, is after), filters referencing deleted or missing forms no longer throw errors when you open feed settings, and admin-only filters now work correctly against multi-value fields.

GravityCharts v1.19.0

GravityCharts receives the same conditional logic improvements: empty date values are handled correctly, filters on deleted forms stop erroring, and admin-only filters work with multi-value fields.

GravityExport v1.10.0

This update to GravityExport enables background exports on sites protected by HTTP Basic Authentication, which is useful for password-protected staging and development environments where background jobs previously couldn’t authenticate themselves. The conditional logic improvements shipping elsewhere in the suite apply here too, covering empty date values, deleted-form filters, and admin-only filters on multi-value fields. A fix also addresses an issue where exports could be incorrectly marked as failed mid-execution on certain hosting environments.

GravityImport v2.10.0

Like GravityExport, GravityImport now supports background imports on sites behind HTTP Basic Authentication. Several import stability issues are also resolved: large imports no longer end with an “Import Incomplete” error when the dataset requires multiple execution cycles, imports no longer get marked as failed mid-execution on certain hosts, and import notifications now send correctly when async notifications are enabled on Gravity Forms 2.9.31.3 or later.

GravityView v2.58.0

This update to GravityView ships internal code improvements only, with no user-facing changes in this version.

GravityView – Advanced Filter Extension v4.6.0

This update to the Advanced Filter Extension carries the same conditional logic improvements as the rest of the suite, and fixes a bug specific to joined forms. When field-level conditional logic targeted a field on a joined form (via the Multiple Forms extension), the condition evaluated against the main form’s row instead of the joined sub-entry, causing the field to render or hide incorrectly. It now evaluates against the joined sub-entry as expected.

GravityView – DataTables Layout v3.7.5

This update to the DataTables Layout fixes a pagination bug. When users switched between different search filter values, DataTables was persisting pagination state across the change, causing tables to open on the wrong page or show no results. Pagination now resets appropriately when filters change.

GravityView – Maps Layout v3.6.5

This update to the Maps Layout restores the Search Bar widget on Views configured to hide data until a search is performed. The widget was being hidden alongside the data, which made the “Hide View data until search is performed” setting unusable.

In summary

GravityBoard introduces Voting with lane-scoped permissions, vote budgets, and GravityView integration; GravityExport and GravityImport gain background-job support for sites behind HTTP Basic Authentication; a broad set of conditional logic improvements lands across GravityBoard, GravityCalendar, GravityCharts, GravityExport, and the Advanced Filter Extension; and the DataTables and Maps layouts each get targeted fixes for pagination and search visibility.

As always, we recommend updating to the latest versions to benefit from these improvements and to ensure compatibility across the GravityKit suite!