Every recorded version, newest first, with what changed in each one.
Latest 2.26.014 versions
Undated · 14 versions
2.26.0
Latest
4 improvements36 changes
Improved
Enhanced conditional logic
Changes to calendars with "Enable security for this calendar" turned on
Improved the security of showing events from another calendar feed
Improved the security of event links and of HTML in events
Changes
This release lets AI assistants manage calendars, updates a calendar as soon as its form is submitted on the same page, and improves conditional logic. It also strengthens security and fixes many issues with event links, dragging events, and the Calendar widget.
Note: Clear your site's page cache after updating so secured calendars show events from other calendar feeds.
AI assistants connected through the [GravityKit MCP]
✨ Improved
Calendars on the same page as their form now show a new entry as soon as the form is submitted with AJAX, without reloading the page or leaving the month being viewed (entries the calendar would not otherwise show, such as those awaiting approval, stay hidden).
Condition dropdowns that search users, entries, or posts now load their choices as soon as they are opened
Conditions using the `{get}` merge tag found no entries or the wrong ones when the value in the page address contained `&`, `+`, or `%` (such as "Research & Development"), and changed other `{get}` merge tags on the page
Conditions on GP Nested Forms fields and other fields that store several users, posts, or entries (such as Dynamic Lookup and Populate Anything fields) were slow on forms with a few hundred entries
"Has any of", "has all of", and "has none of" conditions on Multi Select fields checked only the first selected value
Condition dropdowns could open behind the WordPress admin bar, pressing Enter on a selected choice cleared it, and pressing Enter on the clear button did nothing
When WordPress was set to a language other than English, date conditions showed month names, weekdays, and labels in English, and labels with an apostrophe showed `'` (such as "n'est pas" in French)
Once a date was picked, the weekday names in a date condition's calendar were off by one day in time zones west of UTC (such as the US), and screen readers announced that calendar as "Event".
🔒 Security
Each site now uses its own unique secret, and existing shortcodes and blocks keep working with the old one
Posts created or changed after this update by users who cannot edit calendars need the new secret, so insert the calendar again or have a user who can edit calendars re-save the post
ACF fields on options pages, users, and terms accept only the new secret
The Calendar block shows a secured calendar's secret and preview only to users who can edit calendars
The Elementor widget shows a secured calendar only on pages last saved by a user who can edit calendars or, for calendars secured before this update, on pages unchanged since.
Feed events of secured or turned-off calendars are now available only on pages that show the calendar
Feed addresses on a local or private network are refused when saving the calendar's settings, and are not fetched
Previously saved feeds that are now refused, such as those on port 8443 or with a username and password in the address, are listed in a notice on the calendar's settings screen and recorded in the log.
Event links now open only web addresses, or email, phone, and text message links whose `mailto:`, `tel:`, or `sms:` is typed into the Event URL setting (such as `mailto:{Email:3}`)
With "Allow HTML Content" on, event titles, descriptions, and locations keep links and formatting such as bold text, but drop anything that could run a script and embedded content such as iframes
Turning on "Allow HTML Content" now requires a user who can post unfiltered HTML, such as an administrator on a single site.
Calendars whose events link to a Single Entry page caused a fatal error when that View had been permanently deleted.
The Calendar widget showed an empty calendar on Views that join forms with [Multiple Forms]
With Dynamically Load Events turned on, the Calendar widget showed no events after a search that sent more than one value for a field, such as two ticked checkboxes or a date range.
Calendars added to a View's Single Entry layout with the `[gravitycalendar]` shortcode did not appear when the entry was opened in a lightbox, and the `[gravitycalendar_copy_button]` button there did not copy the calendar's link.
Issues with event links
On sites with permalinks set to "Plain", event links to an entry on another page opened the calendar's own page or a "Page not found" page
Event links built with merge tags lost every query parameter after the first
Custom event links entered without ` such as `example.org/page`, opened a missing page on your own site (links without ` or a leading `/` are now treated as web addresses, so start links to your own site with `/`, such as `/page/{entry_id}`).
Issues with dragging events
Times were saved in the wrong format for the form's Time field, such as 2:00 pm instead of 14:00 in a 24-hour field
On calendars that date events by when entries were created or last updated, dragging an event appeared to move it without saving anything, instead of returning it to its original date (those dates can't be changed).
On sites that display PHP warnings, calendars showed no events from feeds on other websites added with "Display Events from Another Calendar Feed".
2.25.0
1 improvement1 removed16 changes
Improved
Improved security when moving and resizing events on the calendar.
Removed
Deprecated the `gravityview/calendar/scripts/fullcalendar/locales_dir_url` filter. The calendar no longer loads FullCalendar's locale files, so the filter has no effect. Change the calendar's text with a translation or with the `gravityview/calendar/options` filter, whose values still take priority.
Changes
This release displays calendars entirely in their chosen language, resolves several issues with event dates and times, and includes a security improvement; we recommend updating.
✨ Improved
All calendar text, including "all-day", "+3 more", and button tooltips, can now be translated or reworded with a translation plugin such as Loco Translate.
Calendars set to a language other than the site's now download that language's translation automatically when their settings are saved.
🔒 Security
Calendars set to a language other than the site's displayed some text in the wrong language
"all-day", "+3 more", "No events to display", and the Previous and Next button tooltips always appeared in English
Toolbar buttons such as Today, Month, Week, and Day used the site language instead of the calendar's Localization setting.
Timed events from external calendar feeds (such as Google Calendar, Outlook, or iCloud) appeared at their original time in the feed's time zone instead of being converted to the site's time zone like the calendar's own events.
All-day events in calendar subscription links had incorrect end dates: one-day events ended on the day they started, and events without an end date ran until the subscription was last updated.
Resizing an event to span several days on a calendar without an End Date field changed the event's start date instead of undoing the resize.
💻 Developer Updates
The calendar's language downloads respect Foundation's `gk/foundation/translations/disable-download` filter, so a site that turns off translation downloads gets none.
🔧 Updated
[Carbon]( date library to version 2.73.0, which includes the fix for [CVE-2025-22145]( (GravityCalendar does not use the affected function, so sites were not exposed) and restores translation files left out of earlier releases.
[Foundation]
2.24.0
1 improvement16 changes
Improved
Enhanced conditional logic
Changes
This release improves conditional logic, resolves a security issue and several display issues with the Calendar widget, and fixes event times that varied between visitors; we recommend updating.
Note: GravityCalendar now requires Gravity Forms 2.9.4 or newer.
✨ Improved
Calendar widget compatibility with Views that refresh their results without reloading the page, such as when a map is moved.
Conditions on fields that store a user, post, or entry ID (such as Dynamic Lookup, Populate Anything, and Nested Forms fields) now match the name the field displays, limited to records the visitor can see ("is" and "is not" with a number still compare the stored ID)
"Is", "is not", "in", and "not in" conditions on a Product, Option, or Shipping field choice found no entries
Conditions on Entry Date, Date Updated, or Payment Date with a value that was not a date, such as a merge tag for a text field, caused a fatal error on PHP 8
On translated sites, screen readers announced the day, month, and year of date conditions in English.
🔒 Security
The Calendar widget could show entries that the View itself did not display, including every entry in the calendar when "Show only approved entries", a search, or a View filter left the View with no results.
Calendars using an Event field showed events in each visitor's local time, so the time (and sometimes the day) varied between visitors instead of matching the time that was entered.
A calendar placed on the same page after a View's Calendar widget could display that View's events instead of its own, or no events at all if the View used the DataTables layout.
Views with the "Hide View data until search is performed" setting enabled still showed every entry in the Calendar widget before a search when "Display events for" was set to "All View entries".
Content placed after a calendar whose events link to a single entry could behave as though it were on the linked View's page.
🔧 Updated
[Foundation]
2.23.1
10 changes
Changes
This update makes event descriptions accessible to keyboard and screen reader users and fixes calendar layout and block editor preview issues.
Keyboard and screen reader issues with event descriptions
Descriptions in the List and Agenda layouts opened only on mouse hover, not when an event was reached with the keyboard
List events without a link could not be reached with the Tab key
Descriptions stayed open after keyboard focus moved past a link inside them
Screen readers did not announce an event's description when the event had keyboard focus.
Calendar buttons that did not fit on one row, including the default buttons on phones, spilled past the calendar's edge and squeezed the month title onto two lines (they now wrap onto additional rows).
With Gravity Forms 2.x, the GravityCalendar block showed a "This block has encountered an error and cannot be previewed" message in the block editor after a feed was selected (the preview now works and matches the calendar's look on the site).
🔧 Updated
[Foundation]
2.23.0
9 changes
Changes
This release makes conditional logic more accessible and fixes matching on product prices.
Note: GravityCalendar now requires WordPress 6.5 or newer.
✨ Improved
Keyboard and screen reader accessibility of conditional logic: focus stays in place when adding or removing a condition, the AND/OR switch is a single control, and date fields and buttons identify the field they belong to.
Wider Custom Value box in narrow settings panels.
Conditional logic on product prices matched the wrong entries, especially with currencies that use a comma for decimals or place the symbol first (such as Pound Sterling).
The page scrolled when a date picker calendar was opened or closed.
🔧 Updated
[Foundation]
2.22.0
1 new25 changes
New
Added support for the Block Editor's version 3 block API.
Changes
This release adds a GravityCalendar widget for Elementor, allows overriding calendar height when embedding, and fixes some bugs. GravityCalendar now requires WordPress 5.6 or newer.
A GravityCalendar widget for Elementor. Drag it onto the page, pick a calendar, and it renders in the editor as it will on the page — no shortcode to paste. The widget is under the GravityKit category in the widget panel.
Ability to override the calendar's defined height when embedding a calendar
Shortcode: `[gravitycalendar id="5" height="400px"]`. Accepts the same values as the Calendar Height setting — `400px`, `100%`, `10vh` — plus `auto`
GravityCalendar block: a Height field under Calendar Size in the block settings
Elementor widget: a Height slider on the Style tab.
✨ Improved
Calendars whose feed was created outside the settings screen — through the API, or before the Sizing setting existed — logged a PHP warning every time they rendered.
Only administrators could open a form's GravityCalendar feed settings. Now, anyone who can edit forms can edit the feed.
Administrators on sites running the Members plugin could not see the feed settings.
Merge tag pickers were not showing in the calendar feed settings screen.
The Active/Inactive toggle on the All Calendars screen displayed as a plain, unstyled button.
Calendar toolbar buttons showed HTML character codes instead of punctuation in some languages — in French, the "Today" button read "Aujourd'hui" rather than "Aujourd'hui".
The calendar's Filter control did nothing on calendars whose Localization is set to a language other than English.
GravityCalendar block preview in the WordPress editor
Did not recover when a feed was selected again after its settings had failed to load
In the WordPress 7.1 editor
Showed "This block has encountered an error and cannot be previewed" instead of the calendar
Did not switch the active Stack/Grid button of the multi-month layout
Kept the Filter button instead of replacing it with the search box, so events could not be filtered
Opened event tooltips away from their event when the `interactive` option is turned off.
Showed JavaScript errors in the browser console
Clicking the export link in the GravityCalendar Buttons block preview downloaded the calendar file.
🔧 Updated
[Foundation]
2.21.0
1 new17 changes
New
Added filters for the stored calendar: `gk/gravitycalendar/ics-export/cache/enabled` (turn it off site-wide or per feed), `gk/gravitycalendar/ics-export/cache/lifetime` (default: one hour), and `gk/gravitycalendar/ics-export/cache/rebuild-timeout` (default: ten minutes).
Changes
This release speeds up calendar subscriptions, keeps them up to date when entries change, and fixes several subscription and timezone issues.
✨ Improved
Completely reworked how calendar subscriptions are generated to improve performance.
Large calendar feeds now generate without a sweat (tested on forms with more than 20,000 entries)
Now served from a stored copy that refreshes hourly and when you save the feed.
Downloading a single event, or attaching one to a form notification, is much faster.
Conditional logic date filters have a clear button and an improved date picker, and Dynamic Lookup filters use the Lookup plugin's own API when available (Gravity Forms Lookup Field 1.8 or newer).
Events using "Entry Date (Created)" or "Entry Date (Updated)" were displayed in UTC instead of the site's timezone.
Entry changes did not reach calendar subscriptions until the stored copy expired. Now, new, edited, and deleted entries update subscriptions immediately.
Improves support for changes made through GravityView, GravityEdit, GravityRevisions, and GravityImport.
Deleted, disabled, or regenerated feeds returned a server error instead of reporting that the feed no longer exists.
Subscription links kept the site's previous domain after a move. Saving the feed now updates the link without breaking existing subscriptions.
A subscription too large for the server's time limit now properly reports a server error.
Pressing Enter while editing feed settings regenerated the subscription URL and broke existing subscriptions. The URL now changes only when you click "Regenerate URL".
💻 Developer Updates
🔧 Updated
[Foundation]
2.20.0
5 changes
Changes
This release adds support for appending `.ics` to calendar subscription links and fixes subscribed calendars duplicating events on every refresh.
Support for appending `.ics` to the generated calendar subscription link, for calendar applications that only accept URLs ending in `.ics` (existing links continue to work without the suffix).
Events in a calendar subscription received a new identifier on every refresh, causing subscribed calendars to re-add all events on each sync instead of updating the ones they already have.
🔧 Updated
[Foundation]
2.19.0
1 removed8 changes
Removed
Removed an unnecessary database query that ran, and returned no results, every time a calendar's events were loaded.
Changes
This release removes an unnecessary database query from every calendar load and makes the event limit work correctly on calendars that read their events from the database.
✨ Improved
Setting the event limit to a negative value now means "no limit", as it does elsewhere in WordPress, instead of dropping the last event.
The warning logged when the event limit is reached now appears only when entries were actually left out, not when the number of events merely equals the limit.
💻 Developer Updates
The `gravityview/calendar/settings/total-event-limit` filter now applies to events read from the database, where it previously had no effect. The limit defaults to unlimited for database entries, so calendars without a filter callback display exactly as before — but a callback returning a positive number now takes effect on those calendars. Events supplied through the `gravityview/calendar/events/source_data` filter still default to 1000. The limit counts only events the calendar displays, so it is never spent on entries that other filters remove.
🔧 Updated
[Foundation]
2.18.0
1 improvement13 changes
Improved
Enhanced conditional logic
Changes
This release enhances conditional logic filtering, makes the single entry "Go Back" button return to the calendar the event was clicked on, and clears PHP notices that could appear when rendering calendars.
✨ Improved
Calendar events that link to a single entry now remember the page the calendar is on: the "Go Back" button on the Single Entry page returns to the calendar instead of the View's Multiple Entries page, including after editing the entry.
Choice-based filters now offer a searchable dropdown whose results page in as you scroll, so fields with large option lists stay fast and usable instead of trying to render every choice at once. This covers the standard choice fields (Drop Down, Checkbox, Radio, Multi Select) as well as Dynamic Lookup and Populate Anything fields, which draw their options from large external data sets
Use a field merge tag (e.g. `{Threshold:2}`) as a filter value to compare two fields of an entry instead of a static value
Compare against a field on a joined form
The "has ALL of" operator on checkbox and other multi-value fields matched every entry instead of only those containing all the selected values
Switching a condition between single-value and multi-value operators could save a mismatched value shape.
A `_load_textdomain_just_in_time` notice (WordPress 6.7+) appeared because some plugin components loaded translations too early.
Two `Undefined array key "controls"` PHP notices appeared when rendering a calendar whose feed had no header/footer controls setting saved.
Internal Ajax parameters (nonce, date range, calendar ID) appeared in single entry links generated by calendars that load events dynamically.
🔧 Updated
[Foundation]
2.17.0
1 improvement6 changes
Improved
Enhanced conditional logic
Changes
This release improves conditional logic with a searchable picker for multi-selection filters, a new "has NONE of" operator, and a redesigned date picker.
✨ Improved
Value filters that accept multiple selections now use a searchable picker for quicker selection, plus a new "has NONE of" operator for excluding multiple values at once
Conditions on date fields now use a redesigned calendar date picker for easier date entry.
🔧 Updated
[Foundation]
2.16.2
5 changes
Changes
This release fixes missing conditional logic controls under "No Conflict" mode and calendar event tooltips appearing behind the day-of-week header.
Controls for adding new conditional logic rules were missing when "No Conflict" mode was active.
Calendar event tooltips could render behind the day-of-week header.
🔧 Updated
[Foundation]
2.16.1
2 changes
Changes
This hotfix restores the controls for adding new conditional logic rules.
Conditional logic controls missing in the feed settings when no rules had been configured.
2.16.0
1 improvement7 changes
Improved
Enhanced conditional logic
Changes
This release resolves multiple issues with conditional logic, including empty date field values being misinterpreted, filters referencing deleted forms, and admin-only filters applied to multi-value fields.
✨ Improved
Empty field values are no longer treated as today's date when using `is on`, `is not on`, `is before`, or `is after` filters
Filters on deleted or missing forms (e.g. when viewing feed settings for a removed form) no longer trigger errors
Admin-only filters (those suffixed `:disabled_admin`) no longer error out when applied to multi-value fields.
🔧 Updated
[Foundation]
Changelog published by the developer, in their original language.
