https://www.gpldownloads.com/downloads/gravityview-maps-premium-view/changelog/
Latest Updates
Back to GravityView Maps View

GravityView Maps View changelog

Release notes for every version we have on record, newest first.

Latest 3.11.0 · 8 Oct 2026 40 versions Since Oct 2023

2026 15 versions

3.11.0 Latest 8 Oct 2026 1 improved1 security29 changed
Improved
  • Compatibility with GravityView 3.7.0, so a map keeps all its markers when the page also shows the first or last entry of the same View.
Security
  • This release improves map searches and accessibility and resolves many issues with map zoom, map links, "Search as map moves", and markers; it also includes a security fix, so we recommend updating.
Changed
  • Note: GravityMaps now requires PHP 7.4, WordPress 6.5, and GravityView 3.0 or newer.
  • Map area searches during a radius search, which now return only entries that are both inside the radius and visible on the map, in both the Map and DataTables layouts.
  • Screen reader navigation, with the map and entry list now identified as a labeled region named after the View.
  • Keyboard access to the icon picker and its Select Icon and Add Icon buttons in the Map settings.
  • Pagination and sorting, which now keep the map in place while updating its markers.
  • Layout of the radius and unit dropdowns in the Geolocation Radius search field.
  • Map settings in the View editor, now grouped into titled sections with clearer labels.
  • Users who could edit one View could overwrite the saved map positions of a form used by another View they were not allowed to edit.
  • Map markers, the map's starting view, and REST API requests ignored the "Hide View data until search is performed" setting, and invalid map areas, coordinates, or locations without a radius counted as a search.
  • Keyboard visitors could not Tab out of the location input in the Geolocation Radius search field.
  • The map and the Geolocation Radius search field were missing when "Allow REST access" was turned off for a View ("Search as map moves" still needs REST access where GravityView can't update the View in place, such as before version 3.5).
  • "Search as map moves" did not narrow the results on Views without a Search Bar widget or a suitable "Search Everything" field, and radius searches could be ignored when "Search Everything" was limited to visible fields (the visible-fields cases also require GravityView 3.7.0).
  • "Search as map moves" and "Redo search in map" reacted when the map moved on its own (such as after the page loaded, after a marker was clicked, or after a search fitted the map to its results) and behaved incorrectly when switching a map from 3D to 2D.
  • Maps could open at the wrong zoom or position, especially when opened from a link that holds a zoom and position (such as after a reload, from a bookmark, or from an entry link) or when Maximum Zoom was set to "No Maximum".
  • Choosing "No Maximum" for Maximum Zoom in the View editor cleared Default Zoom and reset Minimum Zoom, and opening a View saved with that setting could change its other zoom settings.
  • Radius search issues:
  • Entries at the exact searched location could be left out, as could entries on the opposite side of the world when the radius covered the whole globe
  • An entry's distance could come from an address field outside the radius
  • The radius circle shrank after results reloaded when the search unit was miles.
  • Markers at a latitude or longitude of exactly 0 were left off the map, and such values entered in the entry's geocoding box were not saved.
  • Markers could be missing or out of date on pages with more than one Map View, after a geocode changed on sites with a persistent object cache, or when a page loaded the View's entries more than once.
  • Coordinates that were not valid numbers, such as "39.7 N" or a longitude of 360, could match radius and map area searches and turn the whole map grey.
  • The current location button in the Geolocation Radius search field extended past the location input on some themes, such as Vantage.
  • With Gravity Forms 3.0.3 or newer, entries saved before that update got an extra pin near the center of the country for empty Address fields and matched radius and map area searches.
  • The Distance field was empty in Views that join forms using the Multiple Forms extension.
  • The "Migrate to GravityKit" button stayed disabled with a spinning icon and no error message when the migration request failed.
  • The Map layout templates now fire the gk/gravityview/template/entries/before and gk/gravityview/template/entries/after actions around the map and entry list, as GravityView's other layouts do.
  • The Map layout now declares itself live-refreshing through the gk/gravityview/view/refresh/live filter, so GravityView wraps it in its refresh region and serves its refresh endpoint.
  • Foundation to version 1.36.0.
3.10.5 17 Sep 2026 1 fixed2 changed
Fixed
  • This update fixes styling not applying to the Single Entry page in Map Views.
Changed
  • Single Entry pages of Map Views ignored the Vantage theme, the View's CSS Class setting, and Custom CSS written with VIEW_SELECTOR.
  • Foundation to version 1.32.1.
3.10.4 20 Aug 2026 1 fixed5 changed
Fixed
  • This release fixes marker popups and map search failing on cached map pages, and adds a permission check to the Google Maps API key verification action.
Changed
  • The Google Maps API key verification action ran without confirming that the current user can manage settings.
  • Issues on map pages served from a cache or left open for a long time:
  • Clicking a marker on a map with more than 100 entries showed an empty popup or jumped straight to the entry page
  • Searching within a map on a DataTables layout could return nothing.
  • Foundation to version 1.30.0.
3.10.3 6 Aug 2026 4 changed
Changed
  • This update stops default map pins from disappearing when a site moves or the plugin is installed into a differently named folder.
  • Note: GravityView Maps now requires PHP 7.4 or newer.
  • Default map pins were invisible, and the Default Pin Icon preview in the View editor was broken, when the plugin folder was named something other than gravityview-maps (for example, when installed via Composer) or when the site did not use the standard wp-content folder.
  • Foundation to version 1.28.0.
3.10.2 30 Jul 2026 3 changed
Changed
  • This update resolves a script error that could quietly keep parts of a map page from finishing their setup.
  • Maps with clustered or overlapping markers could log an uncaught JavaScript error ("Must wait for 'idle' event on map before calling markersNearAnyOtherMarker") on page load.
  • Foundation to version 1.27.0.
3.10.1 16 Jul 2026 1 new1 fixed1 removed6 changed
New
  • The Entry Map field settings did not appear in the View editor with GravityView versions older than 2.57 (regression introduced in 3.9.0).
Fixed
  • This release resolves map display issues on DataTables Views and in background browser tabs, restores the Entry Map field settings with GravityView versions older than 2.57, and fixes info windows on Views filtered by URL parameters.
Removed
  • GravityView Maps now uses current GravityView hooks instead of ones deprecated in GravityView 2.55.
Changed
  • On a DataTables View, the Multiple Entries Map widget could rebuild its map each time the table refreshed, leaving an extra, invisible map layered on the canvas and breaking custom code that reads the map object; the widget now keeps a single map instance across refreshes.
  • Maps initialized while their page loaded in a background browser tab could come up broken — a blank gray canvas with no pins and a duplicate map layer; map creation now waits until the tab is visible.
  • The Multiple Entries Map on a DataTables View could remain a blank gray box when no marker pass gave it a viewport; the map now centers itself on its known marker positions.
  • A search with no results left the Multiple Entries Map as an unexplained gray box; the map is now hidden and the "No entries match your request" message is shown instead.
  • Marker info windows and viewport marker loading came up empty on Views filtered by URL parameters, because those requests did not carry the page's query; they now send it along so the View's filters resolve the same way they do for the page itself.
  • Foundation to version 1.25.0.
3.10.0 9 Jul 2026 9 new11 changed
New
  • This release adds a Starting View setting so 3D maps can open in a 2D view, improves load times and reduces page size for maps with large numbers of locations, and resolves several map display and interaction issues.
  • New "Starting View" View setting: when a 3D map type is selected, choose whether the map opens in 3D, in the 2D satellite view, or in the 2D map view (with marker clustering in both 2D views).
  • New "Minimum Zoom for 3D" View setting: only offer the on-map 3D button once the map is zoomed in past a chosen level.
  • New optional viewport loading mode (via the gravityview/maps/viewport-loading filter) that loads only the markers in the visible area and fetches more as you pan or zoom, greatly reducing initial page load on very large maps.
  • Added a REST endpoint, gravityview-maps/v1/views//entries//infowindow, that renders a single entry's info window on demand for lazy-loaded marker popups. It honors custom info window templates and the existing gravityview/maps/infowindow/* filters.
  • Added gravityview/maps/infowindow/lazy-load and gravityview/maps/infowindow/lazy-load/threshold filters to control when info window content loads on demand (default: on for maps with more than 100 markers).
  • Added gravityview/maps/render-entries-list filter to skip rendering the directory entry list on a Map View while still placing every marker, for map-only layouts that hide the list.
  • Added gravityview/maps/viewport-loading and gravityview/maps/viewport-loading/initial-limit filters, plus a REST endpoint gravityview-maps/v1/views//markers that returns the markers within a latitude/longitude bounding box, to power viewport loading.
  • Added gravityview/maps/viewport-loading/dataset-bounds, gravityview/maps/viewport-loading/dataset-bounds-scan-limit, and gravityview/maps/viewport-loading/dataset-bounds-cache-context filters to control how a bare-URL viewport map is framed.
Changed
  • 3D marker popups now include a close button, and the map shows a loading indicator while the 3D view initializes.
  • Switching between 2D and 3D keeps the imagery consistent: leaving 3D opens the 2D map with the same satellite imagery and labels state, and the 3D view opens with labels when the 2D map was showing them.
  • Zooming out in 3D past the "Minimum Zoom for 3D" level returns the map to the 2D view.
  • Map marker info windows now load on demand when a marker is clicked, rather than being built into the page for every entry up front; 3D marker popups fetch their content the same way.
  • Maps with a large number of locations could exhaust available memory and fail with a fatal error, or load slowly, because per-entry data was accumulated incorrectly while preparing markers.
  • On GravityView 3.x, a single entry's Ratings & Reviews section and "Review this entry" form could appear below a Map View.
  • On maps with clustering, the first click on a stack of overlapping pins opened an info window or jumped to a linked entry rather than fanning the pins out (spiderfying) for selection.
  • Bundled marker icons saved under a site's previous domain or protocol made pins invisible after the site moved; they now load from the current plugin location.
  • Switching to 3D while the map was in fullscreen left the 3D view hidden until fullscreen was exited.
  • Entering 3D over higher-elevation cities could place the camera at ground level or underground; the camera now uses real terrain elevation when the site's Google key has the Elevation API enabled, and otherwise enters at a safe city-scale view.
  • On maps with more locations than the 3D view can display at once, pins visible in 2D could be missing after switching to 3D because distant markers used up the 3D marker limit; markers in the current view now take priority.
3.9.0 25 Jun 2026 4 new1 fixed8 changed
New
  • New features for the Geolocation Radius search (requires GravityView 2.57 or newer):
  • Added gk/gravitymaps/fields/distance/output filter to modify the Distance field output.
  • Added gk/gravitymaps/search/radius/sort-by-distance filter to programmatically enable or disable distance sorting for radius search results.
  • Adds Map View settings to GravityView's View inspector REST API under the maps.* namespace, so REST and AI abilities clients can read, configure, and discover them through the template_settings endpoints (requires GravityView 3.0.0 or newer).
Fixed
  • This release lets visitors see and sort by how far each entry is from their searched location, and fixes radius and map area searches returning inaccurate results in some setups.
Changed
  • A Distance field that shows how far each entry is from the searched location, in the unit used for the search (kilometers or miles)
  • A View setting to sort radius search results by distance, showing the nearest entries first.
  • Map area searches ("Search as the map moves") could return entries outside the visible area when the Search Bar's search mode was set to match any field.
  • Radius searches could return inaccurate results in some cases.
  • Map area searches could prevent other plugins from applying their own changes to search results.
  • A deprecation notice was logged when editing Maps field settings in the View editor with GravityView 2.55 or newer.
  • A PHP error could occur when another plugin or theme registered a script without a source URL.
  • Foundation to version 1.24.2.
3.8.0 4 Jun 2026 3 new1 fixed10 changed
New
  • Added gk/gravitymaps/maps/3d/options and gk/gravitymaps/maps/3d/marker-cap PHP filters to customize the 3D Maps settings and the maximum number of 3D markers rendered in the viewport.
  • Added the gk/gravitymaps/map-services/google-maps/libraries PHP filter to control which Google Maps JavaScript API libraries are loaded.
  • Added gk.maps.services.google_maps.maps3d.settings, gk.maps.services.google_maps.maps3d.create_marker_options, and gk.maps.services.google_maps.maps3d.create_pin_options JavaScript filters, and the gk.maps.services.google_maps.maps3d.fallback JavaScript action, to customize 3D markers and pins and to react when the map falls back to 2D.
Fixed
  • This release adds photorealistic 3D map types and an interactive location picker for Edit Entry, and fixes several map search and geocoding issues.
Changed
  • "3D Satellite" and "3D Hybrid" map types that render Google's photorealistic 3D Maps, with a control to switch between 2D and 3D views.
  • An interactive map on the Edit Entry screen and in the Gravity Forms entry view for setting an entry's exact location.
  • The "Search as map moves" and "Redo search in map" features could return no results when the GravityView REST API was enabled for a View but disabled globally.
  • Map searches could return entries outside the visible area when the map crossed the 180° meridian, such as Pacific-centered views.
  • "Search as map moves" could intermittently stop running new searches after the map moved, leaving stale results.
  • The Map widget on a DataTables View could intermittently fail to render, and logged-in administrators could see an incorrect notice that no addresses were geocoded.
  • Editing an entry's location in Gravity Forms with a non-numeric latitude or longitude could delete the saved coordinates instead of rejecting the value.
  • Geocoding an entry with out-of-range or malformed coordinates could return a server error on PHP 8 instead of a clear validation message.
  • Map searches could behave unexpectedly when the map bounds contained invalid latitude or longitude values.
  • Foundation to version 1.21.0.
3.7.0 28 May 2026 1 fixed4 changed
Fixed
  • This release fixes Single Entry Map layout spacing and field output filter context, and improves the REST API notice for Map Views.
Changed
  • Replaced the REST API confirmation pop-up for Map Views with a clearer admin notice that lists the affected Views and lets you enable REST API access for them in one click.
  • Single Entry Map title fields were not passing the current template context to GravityView field output filters.
  • Single Entry Map layouts did not match List View spacing and could stretch featured images to full width.
  • Foundation to version 1.20.0.
3.6.5 23 Apr 2026 3 changed
Changed
  • This release restores the Search Bar widget on Views that hide data until search.
  • The Search Bar widget was hidden when the "Hide View data until search is performed" setting was enabled.
  • Foundation to version 1.16.0.
3.6.4 19 Mar 2026 1 fixed1 removed
Fixed
  • This update fixes a map display issue where cluster icons were not properly cleared when zooming in or out.
Removed
  • Marker cluster icons were not removed when zooming, causing them to accumulate on the map.
3.6.3 5 Mar 2026 1 fixed2 changed
Fixed
  • This release fixes geolocation radius search using stale coordinates on consecutive searches and resolves PHP deprecation warnings with Gravity Forms 2.9.29+.
Changed
  • Geolocation radius search used coordinates from the first search on every subsequent search, ignoring the new location.
  • PHP deprecation warnings from Gravity Forms 2.9.29+ when rendering address field values.
3.6.2 19 Feb 2026 1 fixed2 changed
Fixed
  • This update fixes the Map Type setting not being applied on the frontend.
Changed
  • Map Type setting (Satellite, Hybrid, Terrain) was ignored on the frontend, always defaulting to the road map view.
  • Foundation to version 1.11.0.
3.6.1 12 Feb 2026 3 changed
Changed
  • This update addresses a search issue causing incorrect Map View results.
  • Successive Map View searches showing incorrect results caused by duplicate URL parameters.
  • Foundation to version 1.10.0.

2025 7 versions

3.6.0 20 Nov 2025 1 new1 fixed2 changed
New
  • Google Maps API key validation under GravityKit → Settings → Gravity Maps is now more reliable, with added checks to help confirm your key is configured correctly.
Fixed
  • This release makes Google Maps API key checks more reliable and fixes an issue where map state would not persist when switching between layouts.
Changed
  • Geolocation radius selection, map zoom level, and other map state is no longer reset when navigating between Multiple Entries and Single Entry layouts.
  • Foundation to version 1.7.0.
3.5.0 9 Oct 2025 1 new1 improved2 changed
New
  • This update adds integration with the DataTables extension and improves navigation from single to multiple entries by preserving map state.
Improved
  • Compatibility with the DataTables extension in server-side processing mode - the Multiple Entries Map widget and the table now remain synchronized in both directions.
Changed
  • "Go Back" link on the Single Entry layout with the Map view type now preserves URL query parameters when returning to the Multiple Entries layout.
  • Foundation to version 1.6.0.
3.4.0 11 Sep 2025 1 fixed2 changed
Fixed
  • This update makes radius-based searches more consistent by always narrowing results and fixes the display of the Geolocation Radius label in the Search Bar.
Changed
  • Radius searches are now combined with other conditions using an AND clause instead of OR, ensuring results are consistently restricted by the geolocation filter.
  • Geolocation Radius field label not displaying in the Search Bar when the "Show Label" option is enabled.
3.3.0 4 Sep 2025 4 new1 improved11 changed
New
  • This release adds improved keyboard and display controls for radius search, and resolves multiple issues with map search actions, filter clearing, marker interactions, and spiderfy behavior.
  • Added gk/gravitymaps/search/reserved-args filter to modify the list of reserved URL parameters used by the Search Bar widget.
  • Added gk.maps.radius_circle.options and gk.maps.radius_marker.options JavaScript filters to customize the appearance of the radius search circle and center marker.
  • New GravityKit global settings for logging configuration (level, type, cleanup schedule, retention)
Improved
  • Performance improvements and bug fixes.
Changed
  • Keyboard support for selecting the top autocomplete suggestion and applying geocoded results to related fields (address, postcode, lat/lng).
  • "Hide radius search circle" setting in the View editor to remove the red circle overlay shown during radius searches.
  • "Redo search" and "Search as map moves" actions not working in Views using the DIY layout.
  • Error triggered when pressing "Enter" in the Radius Search input.
  • Clearing filters in the Search Bar would not update the URL to remove location parameters.
  • The "Redo search in map" functionality no longer causes search fields and filters to break.
  • Overlapping markers now spiderfy correctly, making it clear when multiple pins are at the same location.
  • Marker click handling when clustering is enabled or disabled, ensuring clusters zoom correctly and info windows or single entry views open reliably.
  • Radius search not working when using custom latitude/longitude field mapping via the gk/gravitymaps/markers/coordinates/fields-ids filter.
  • Foundation to version 1.3.1:
  • A unified way to display admin notices across all GravityKit products
3.2.9 16 Aug 2025 1 new
New
  • JavaScript error introduced in 3.2.8.
3.2.8 14 Aug 2025 1 new1 improved3 changed
New
  • Support for the Layout Builder layout when using the Pinned Map setting.
Improved
  • This release improves compatibility with the Layout Builder and refines the search and location filtering experience.
Changed
  • Search Bar clear button not properly resetting radius search and location filter parameters.
  • Geolocation autocomplete incorrectly adding a county into a city input.
  • Bounds search not always being treated as a search request when using "Hide Until Search" setting.
3.2.7 8 May 2025 2 fixed2 changed
Fixed
  • This update fixes a performance issue and resolves a PHP notice in WordPress 6.8.
  • Fixed repeated asset enqueuing and redundant localization, which slowed down page load.
Changed
  • PHP notice in WordPress 6.8 related to early product translation initialization.
  • Foundation to version 1.2.25.

2024 13 versions

3.2.6 21 Nov 2024 1 fixed2 changed
Fixed
  • This hotfix update addresses a non-critical PHP notice in WordPress 6.7 and newer.
Changed
  • PHP notice in WordPress 6.7 caused by initializing product translations too early.
  • Foundation to version 1.2.21.
3.2.5 8 Nov 2024 1 fixed1 changed
Fixed
  • This update fixes a compatibility issue with GravityView version 2.31 and newer.
Changed
  • Compatability with GravityView version 2.31 and newer.
3.2.4 6 Nov 2024 1 new1 fixed3 changed
New
  • Added the ability to use wp.hooks.addAction() and wp.hooks.removeAction() for controlling marker functionality and other aspects of the Google Maps script.
Fixed
  • This release fixes a rendering issue and corrects the URL structure for markers linking to single entries in embedded Views.
Changed
  • Zoomed-out map view showed both clusters and individual markers.
  • Map markers in embedded Views incorrectly linked to single entries using the View's custom post URL instead of the parent page/post URL.
  • Foundation to version 1.2.20.
3.2.3 12 Sep 2024 1 fixed2 changed
Fixed
  • This update fixes performance issues causing the View and View editor to time out.
Changed
  • View and View editor timing out due to inefficient database queries.
  • Foundation and TrustedLogin to versions 1.2.18 and 1.9.0, respectively.
3.2.2 25 Aug 2024 2 changed
Changed
  • This update addresses a fatal error related to the internal caching process.
  • Fatal error that could occur during View loading due to a caching issue.
3.2.1 19 Aug 2024 2 changed
Changed
  • This update resolves a fatal error related to multiple geolocation data sources.
  • Fatal error due to an undefined variable.
3.2.0 19 Aug 2024 2 improved3 changed
Improved
  • This release introduces support for multiple geolocation data sources, ensuring seamless map display of entries even when forms are updated to use different address autocompletion and geolocation add-ons.
  • Support for multiple geolocation data sources configured for Address fields, including Gravity Forms Address Autocomplete by Gravity Wiz and the Geolocation Add-On by Gravity Forms.
Changed
  • Data migration between geolocation data sources, consolidating data when multiple form add-ons have been used for geolocation.
  • The Search Bar now includes additional radius search distance values.
  • Foundation and TrustedLogin to versions 1.2.17 and 1.8.0, respectively.
3.1.7 22 May 2024 2 new1 improved4 fixed6 changed
New
  • Added an option to subscribe to GravityKit's newsletter from the Manage Your Kit screen.
  • Added a setting in GravityKit > Settings > GravityKit to specify the GravityKit menu position in the Dashboard.
Improved
  • Improved internal check for product updates that could still interfere with third-party plugin updates. Thanks, Aaron!
Fixed
  • This release addresses several bugs and updates internal components to improve performance and compatibility.
  • Fixed a bug that prevented WordPress from loading third-party plugin translations after their updates. Thanks, Jérôme!
  • Fixed a bug that hid third-party plugin updates on the Plugins and Updates pages.
  • Resolved a dependency management issue that incorrectly prompted for a Gravity Forms update before activating, installing, or updating GravityKit products.
Changed
  • Missing zoom levels 18–21 for the "Maximum Zoom" View setting.
  • Fatal error when checking Google Maps API key on PHP 8.1.
  • Multiple markers for a single entry not displaying on the map.
  • Multiple address fields triggering geocoding when using address autocompletion add-ons from Gravity Wiz and Gravity Forms.
  • Foundation to version 1.2.15.
  • Success message now shows correct product name after activation/deactivation.
3.1.6 29 Mar 2024 1 fixed2 changed
Fixed
  • This update fixes a PHP 8.2 deprecation notice and a fatal error when customizing themes or editing posts/pages.
Changed
  • PHP 8.2 deprecation notice.
  • Fatal error when customizing themes or editing posts/pages.
3.1.5 25 Mar 2024 1 fixed5 changed
Fixed
  • This release addresses issues related to automatic address geocoding and merge tag processing, fixes JavaScript errors, and restricts the loading of extension's assets to specific locations.
Changed
  • Automatic address geocoding no longer happens outside the View.
  • Merge tags are now correctly processed inside the marker's info window.
  • Form fields with latitude and longitude coordinates can once again be specified via the gk/gravitymaps/markers/coordinates/fields-ids filter.
  • JavaScript errors on Gravity Forms admin screens and when loading the View have been resolved.
  • Extension's JavaScript files are now only loaded where needed.
3.1.4 12 Mar 2024 2 new1 improved5 changed
New
  • This release introduces a new feature that allows for the automatic geocoding of entries. It also improves performance and addresses critical issues related to pagination, the saving of Views, and compatibility with the Multiple Forms extension.
  • Gk/gravitymaps/marker/auto-geocode filter to control whether the entry is automatically geocoded if no latitude/longitude coordinates are found.
Improved
  • Performance issues.
Changed
  • A setting to control the automatic geocoding of entries when they are missing latitude and longitude coordinates.
  • Pagination links not working.
  • Fatal error when saving Views.
  • Fatal error when the Maps layout is used in combination with the Multiple Forms extension.
  • Developer Updates:
3.1.3 5 Mar 2024 1 improved2 fixed1 removed10 changed
Improved
  • The release improves functionality by adding new features, resolving display issues, and updating internal components to enhance performance and compatibility.
Fixed
  • Fixed a JavaScript warning that occurred when deactivating license keys and when viewing products without the necessary permissions.
  • Resolved PHP warning messages on the Plugins page and Updates pages, and when deactivating the last active product with Foundation installed.
Removed
  • Database options that are no longer used are now automatically removed.
Changed
  • A setting to hide the Geolocation Radius Unit that is not the default one being used.
  • Google Maps API key check verifies if the Places API service is enabled
  • Pagination when using the "Search as map moves" feature.
  • When available, coordinates from Gravity Wiz's Address Autocomplete perk are reused for entries not previously geocoded by GravityView Maps.
  • An issue where Default Unit field was not being displayed when using List view or Table view.
  • Map disappearance when "Hide view data" was checked and no entries were found upon moving the map.
  • Foundation and TrustedLogin to versions 1.2.11 and 1.7.0, respectively.
  • GravityKit product updates are now showing on the Plugins page.
  • Transients are now set and retrieved correctly when using object cache plugins.
  • GravityKit products that are already installed can now be activated without a valid license.
3.1.2 12 Jan 2024 4 changed
Changed
  • This update addresses issues with Multiple Forms and Autocomplete fields.
  • A fatal error that occurred when using ZIP Code as the Join Field for Multiple Forms.
  • A JavaScript error that happened when using the Autocomplete field without the Places API enabled.
  • A JavaScript error related to using Autocomplete on the Address Form field.

2023 5 versions

3.1.1 27 Dec 2023 3 changed
Changed
  • Custom map icons based on specific field values, also known as choice-based markers, were not displaying on the map.
  • JavaScript errors in the Gravity Forms form editor caused by GravityView Maps.
  • Foundation to version 1.2.6.
3.1 9 Nov 2023 6 new1 improved1 fixed2 removed18 changed
New
  • Request a user's location to trigger a radius search
  • "Request Location" setting, enabling a View to immediately request a user’s location when the page loads (defaults to disabled)
  • Gk/gravitymaps/markers/coordinates/fields-ids Filter to use latitude and longitude fields
  • Gk/gravitymaps/maps/service-factory/get-map-service-instance-for-view filter to modify the map service instance for a View
  • Gk/gravitymaps/maps/service-factory/get-map-service-class-for-view filter to modify the map service class for a View
  • JavaScript hooks for Maps and Markers
Improved
  • Support for displaying multiple maps on the same page
Fixed
  • Fatal error when Views have custom info box content
Removed
  • Gravityview/maps/markers/lat_long/fields_id filter (use gk/gravitymaps/markers/coordinates/fields-ids instead)
  • Gravityview/maps/render/google_api_key filter (use gk/gravitymaps/map-services/google-maps/api_key instead)
Changed
  • Created new "Radius Search Settings" settings section
  • Developer Updates:
  • Gk.maps.controllers.marker.before_process_map
  • Gk.maps.controllers.marker.after_process_map
  • Gk.maps.controllers.marker.create
  • Gk.maps.controllers.marker.after_create
  • Gk.maps.controllers.marker.on_view_entry_mouse_enter
  • Gk.maps.controllers.map.bind_observer_to_maps
  • Gk.maps.controllers.map.update_data
  • Gk.maps.controllers.map.get_data
  • Gk.maps.controllers.map.update_settings
  • Gk.maps.controllers.map.get_settings
  • Gk.maps.controllers.map.create_map
  • Gk.maps.controllers.map.after_create_map
  • Gk.maps.controllers.map.set_zoom
  • Gk.maps.controllers.map.set_center
  • Gk.maps.controllers.map.get_maps
  • Gk.maps.controllers.map.get_search_maps
3.0.3 26 Oct 2023 2 fixed
Fixed
  • Merge tags not working in the Map Info Box content field
  • PHP 8.1+ deprecation notice
3.0.2 25 Oct 2023 2 fixed
Fixed
  • Views created from the Business Map Listing preset did not have any fields configured
  • PHP 8.2+ deprecation notice
3.0.1 19 Oct 2023 3 fixed
Fixed
  • Business Map Listing preset not properly loading when creating a new View
  • Incorrect image scaling in the marker info box
  • Entry Map field not working inside the Single Entry layout