Every recorded version, newest first, with what changed in each one.
Latest 3.12.015 versions
Undated · 15 versions
3.12.0
Latest
10 changes
Changes
This release improves the security of geocoding errors and fixes text that stayed in English on non-English sites and PHP 8.4 notices on pages with a map.
✨ Improved
Clearer wording for the Default Radius and Radius Unit Display tooltips in the Map settings.
🔒 Security
When WordPress was set to a language other than English, some text always appeared in English
The help text under the Subheading, Image, and Other Fields areas of the Map layout's Single Entry screen in the View editor
The Default Radius and Radius Unit Display tooltips, and the second sentence of the Maximum Zoom tooltip, in the Map settings
The notice about a form with more than one source of location data
The Latitude and Longitude entry fields added for each address field.
On PHP 8.4 or newer, pages with a map showed PHP deprecation notices ("Implicitly marking parameter ... as nullable is deprecated").
3.11.0
1 improvement34 changes
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.
Changes
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.
Note: GravityMaps now requires PHP 7.4, WordPress 6.5, and GravityView 3.0 or newer.
✨ Improved
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.
🔒 Security
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]
The "Migrate to GravityKit" button stayed disabled with a spinning icon and no error message when the migration request failed.
💻 Developer Updates
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.
🔧 Updated
[Foundation]
3.10.5
4 changes
Changes
This update fixes styling not applying to the Single Entry page in Map Views.
Single Entry pages of Map Views ignored the Vantage theme, the View's CSS Class setting, and Custom CSS written with `VIEW_SELECTOR`.
🔧 Updated
[Foundation]
3.10.4
5 changes
Changes
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.
🔧 Updated
[Foundation]
3.10.3
5 changes
Changes
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.
🔧 Updated
[Foundation]
3.10.2
4 changes
Changes
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.
🔧 Updated
[Foundation]
3.10.1
11 changes
Changes
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.
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).
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.
💻 Developer Updates
GravityView Maps now uses current GravityView hooks instead of ones deprecated in GravityView 2.55.
🔧 Updated
[Foundation]
3.10.0
8 new14 changes
New
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.
Changes
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.
3D marker popups now include a close button, and the map shows a loading indicator while the 3D view initializes.
✨ Improved
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.
💻 Developer Updates
3.9.0
4 new11 changes
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).
Changes
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.
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.
💻 Developer Updates
🔧 Updated
[Foundation]
3.8.0
3 new13 changes
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.
Changes
This release adds photorealistic 3D map types and an interactive location picker for Edit Entry, and fixes several map search and geocoding issues.
"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.
💻 Developer Updates
🔧 Updated
[Foundation]
3.7.0
7 changes
Changes
This release fixes Single Entry Map layout spacing and field output filter context, and improves the REST API notice for Map Views.
✨ Improved
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.
🔧 Updated
[Foundation]
3.6.5
4 changes
Changes
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.
🔧 Updated
[Foundation]
3.6.4
2 changes
Changes
This update fixes a map display issue where cluster icons were not properly cleared when zooming in or out.
Marker cluster icons were not removed when zooming, causing them to accumulate on the map.
3.6.3
3 changes
Changes
This release fixes geolocation radius search using stale coordinates on consecutive searches and resolves PHP deprecation warnings with Gravity Forms 2.9.29+.
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
4 changes
Changes
This update fixes the Map Type setting not being applied on the frontend.
Map Type setting (Satellite, Hybrid, Terrain) was ignored on the frontend, always defaulting to the road map view.
🔧 Updated
[Foundation]
Changelog published by the developer, in their original language.
