Maps Premium View Changelog

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.

🐛 Fixed

• 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 to version 1.25.0.

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.

🚀 Added

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

🐛 Fixed

• 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

• Added a REST endpoint, gravityview-maps/v1/views/<view_id>/entries/<entry_id>/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/<view_id>/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.

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.

🚀 Added

• New features for the Geolocation Radius search (requires GravityView 2.57 or newer):
  • 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.

🐛 Fixed

• 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

• 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).

🔄 Updated

• Foundation to version 1.24.2.

This release adds photorealistic 3D map types and an interactive location picker for Edit Entry, and fixes several map search and geocoding issues.

🚀 Added

• "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.

🐛 Fixed

• 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

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

🔄 Updated

• Foundation to version 1.21.0.

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.

🐛 Fixed

• 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 to version 1.20.0.

This release restores the Search Bar widget on Views that hide data until search.

🐛 Fixed

• The Search Bar widget was hidden when the "Hide View data until search is performed" setting was enabled.

🔄 Updated

• Foundation to version 1.16.0.

This update fixes a map display issue where cluster icons were not properly cleared when zooming in or out.

🐛 Fixed

• Marker cluster icons were not removed when zooming, causing them to accumulate on the map.

This release fixes geolocation radius search using stale coordinates on consecutive searches and resolves PHP deprecation warnings with Gravity Forms 2.9.29+.

🐛 Fixed

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

This update fixes the Map Type setting not being applied on the frontend.

🐛 Fixed

• Map Type setting (Satellite, Hybrid, Terrain) was ignored on the frontend, always defaulting to the road map view.

🔄 Updated

• Foundation to version 1.11.0.

This update addresses a search issue causing incorrect Map View results.

🐛 Fixed

• Successive Map View searches showing incorrect results caused by duplicate URL parameters.

🔄 Updated

• Foundation to version 1.10.0.

This release makes Google Maps API key checks more reliable and fixes an issue where map state would not persist when switching between layouts.

✨ Improved

• 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

• Geolocation radius selection, map zoom level, and other map state is no longer reset when navigating between Multiple Entries and Single Entry layouts.

🔄 Updated

• Foundation to version 1.7.0.

This update adds integration with the DataTables extension and improves navigation from single to multiple entries by preserving map state.

🚀 Added

• Compatibility with the DataTables extension in server-side processing mode - the Multiple Entries Map widget and the table now remain synchronized in both directions.

✨ Improved

• "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.

🔄 Updated

• Foundation to version 1.6.0.

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.

✨ Improved

• Radius searches are now combined with other conditions using an AND clause instead of OR, ensuring results are consistently restricted by the geolocation filter.

🐛 Fixed

• Geolocation Radius field label not displaying in the Search Bar when the "Show Label" option is enabled.

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

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

🐛 Fixed

• "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.

💻 Developer Updates

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

🔧 Updated

• Foundation to version 1.3.1:
  • New GravityKit global settings for logging configuration (level, type, cleanup schedule, retention);
  • A unified way to display admin notices across all GravityKit products;
  • Performance improvements and bug fixes.

🐛 Fixed

• JavaScript error introduced in 3.2.8.

This release improves compatibility with the Layout Builder and refines the search and location filtering experience.

✨ Added

• Added: Support for the Layout Builder layout when using the Pinned Map setting.

🐛 Fixed

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

This update fixes a performance issue and resolves a PHP notice in WordPress 6.8.

🐛 Fixed

• Fixed repeated asset enqueuing and redundant localization, which slowed down page load.
• PHP notice in WordPress 6.8 related to early product translation initialization.

🔄 Updated

• Foundation to version 1.2.25.

This hotfix update addresses a non-critical PHP notice in WordPress 6.7 and newer.

🐛 Fixed

• PHP notice in WordPress 6.7 caused by initializing product translations too early.

🔄 Updated

• Foundation to version 1.2.21.

This update fixes a compatibility issue with GravityView version 2.31 and newer.

🐛 Fixed

• Compatability with GravityView version 2.31 and newer.

This release fixes a rendering issue and corrects the URL structure for markers linking to single entries in embedded Views.

🐛 Fixed

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

🔧 Updated

• Foundation to version 1.2.20.

💻 Developer Updates

• Added the ability to use wp.hooks.addAction() and wp.hooks.removeAction() for controlling marker functionality and other aspects of the Google Maps script.

This update fixes performance issues causing the View and View editor to time out.

🐛 Fixed

• View and View editor timing out due to inefficient database queries.

🔧 Updated

• Foundation and TrustedLogin to versions 1.2.18 and 1.9.0, respectively.

This update addresses a fatal error related to the internal caching process.

🐛 Fixed

• Fatal error that could occur during View loading due to a caching issue.

This update resolves a fatal error related to multiple geolocation data sources.

🐛 Fixed

• Fatal error due to an undefined variable.

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.

🚀 Added

• 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.
• Data migration between geolocation data sources, consolidating data when multiple form add-ons have been used for geolocation.

✨ Improved

• The Search Bar now includes additional radius search distance values.

🔧 Updated

• Foundation and TrustedLogin to versions 1.2.17 and 1.8.0, respectively.

This release addresses several bugs and updates internal components to improve performance and compatibility.

🚀 Added

• Missing zoom levels 18–21 for the "Maximum Zoom" View setting.

🐛 Fixed

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

🔧 Updated

• Foundation to version 1.2.15.
  • 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 internal check for product updates that could still interfere with third-party plugin updates. Thanks, Aaron!
  • 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.
  • Success message now shows correct product name after activation/deactivation.
  • Resolved a dependency management issue that incorrectly prompted for a Gravity Forms update before activating, installing, or updating GravityKit products.

This update fixes a PHP 8.2 deprecation notice and a fatal error when customizing themes or editing posts/pages.

🐛 Fixed

• PHP 8.2 deprecation notice.
• Fatal error when customizing themes or editing posts/pages.

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.

🐛 Fixed

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

✨ Improved

• Extension's JavaScript files are now only loaded where needed.

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.

🚀 Added

• A setting to control the automatic geocoding of entries when they are missing latitude and longitude coordinates.

🐛 Fixed

• Pagination links not working.
• Fatal error when saving Views.
• Performance issues.
• Fatal error when the Maps layout is used in combination with the Multiple Forms extension.

Developer Updates:

• Added: gk/gravitymaps/marker/auto-geocode filter to control whether the entry is automatically geocoded if no latitude/longitude coordinates are found.

The release improves functionality by adding new features, resolving display issues, and updating internal components to enhance performance and compatibility.

🚀 Added

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

✨ Improved

• When available, coordinates from Gravity Wiz's Address Autocomplete perk are reused for entries not previously geocoded by GravityView Maps.

🐛 Fixed

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

🔧 Updated

• Foundation and TrustedLogin to versions 1.2.11 and 1.7.0, respectively.
  • GravityKit product updates are now showing on the Plugins page.
  • Database options that are no longer used are now automatically removed.
  • 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.
  • 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.

This update addresses issues with Multiple Forms and Autocomplete fields.

🐛 Fixed

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

🐛 Fixed

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

🔄 Updated

• Foundation to version 1.2.6.

• Added: Request a user's location to trigger a radius search
• Added: "Request Location" setting, enabling a View to immediately request a user’s location when the page loads (defaults to disabled)
  • Created new "Radius Search Settings" settings section
• Improved: Support for displaying multiple maps on the same page
• Fixed: Fatal error when Views have custom info box content

Developer Updates:

• Added: gk/gravitymaps/markers/coordinates/fields-ids Filter to use latitude and longitude fields
• Added: gk/gravitymaps/maps/service-factory/get-map-service-instance-for-view filter to modify the map service instance for a View
• Added: gk/gravitymaps/maps/service-factory/get-map-service-class-for-view filter to modify the map service class for a View
• Added: JavaScript hooks for Maps and Markers
  • 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
• Deprecated: gravityview/maps/markers/lat_long/fields_id filter (use gk/gravitymaps/markers/coordinates/fields-ids instead)
• Deprecated: gravityview/maps/render/google_api_key filter (use gk/gravitymaps/map-services/google-maps/api_key instead)

• Fixed: Merge tags not working in the Map Info Box content field
• Fixed: PHP 8.1+ deprecation notice

• Fixed: Views created from the Business Map Listing preset did not have any fields configured
• Fixed: PHP 8.2+ deprecation notice

• Fixed: Business Map Listing preset not properly loading when creating a new View
• Fixed: Incorrect image scaling in the marker info box
• Fixed: Entry Map field not working inside the Single Entry layout

• Fixed: UI elements not showing on the Map when JavaScript assets are not loaded in the correct order
• Fixed: Entries and pins stop loading after seeing no results when using the "search as map moves" feature
• Fixed: Server error when using the "search as map moves" feature if the View's "direct access" setting is not set to "public"
• Fixed: CSS styling issue affecting map zoom controls
• Updated: Foundation to version 1.2.4

Developer Updates:

• Added: CSS class gk-hide-individual-entries to the gv-map container when no fields are configured in the Map View
• Modified:
  • Template files updated to use the GravityView 2.0 template structure
  • Templates now have access to the $gravityview and GVTemplate_Context global objects
  • Template location changed from templates/ to templates/views/map/
  • Base template for the Map View renamed from map-view.php to map.php
• Renamed hooks while maintaining backward compatibility:
  • gravityview_entry_class to gravityview/template/map/entry/class
  • gravityview_map_body_before to gravityview/template/map/body/before
  • gravityview_map_body_after to gravityview/template/map/body/after
  • gravityview_map_entry%sbefore to gravityview/template/map/entry%sbefore
  • gravityview_map_entry%safter to gravityview/template/map/entry%safter
  • gravityview_map_render_div to gk/gravitymaps/render/map-canvas

• Improved: Support for RTL languages
• Updated: Foundation to version 1.2.2

• Fixed: Geolocation search was not properly setting necessary mapping parameters for both "Any" and "All" search modes
• Fixed: A search page with no results did not show a map, making it impossible for users to scroll the map to search different areas
• Fixed: Prevent a couple of errors when using older versions of GravityView with Maps

• Improved: Minimum, Maximum and Default Zoom setting fields now restrict each other's values to prevent invalid configurations
• Fixed: Geolocation search params are properly respected on both Any and All search modes
• Fixed: Geolocation Radius label was not displayed if the field is not empty
• Fixed: Default Zoom is now applied to the map when the View is loaded
• Updated: Foundation to version 1.1.1

• Fixed: A notice requesting REST API access shows up for all View types, not just Views with maps
• Fixed: The front-end notice alerting administrators that the REST API setting is disabled was not worded clearly
• Fixed: Using custom longitude and latitude values on forms without an Address field
• Updated: Foundation to version 1.1.0

Developer Notes:

• Added: Marker::from_address_field() and Marker::from_coordinate_fields() methods to construct a Marker object from an Address field or Longitude/Latitude fields
• Added: base.js file to the assets/js directory, used to handle global JS hooks
• Added: JavaScript filter to modify the options used to build a Marker: gk.maps.marker_options
• Added: JavaScript action after a Marker is added: gk.maps.after_add_marker
• Modified: Renamed many JavaScript hooks to use standard GravityKit naming structure:
  • gravitykit/maps/autocomplete_field_id => gk.maps.autocomplete_field_id
  • gravitykit/maps/autocomplete_input_id => gk.maps.autocomplete_input_id
  • gravitykit/maps/autocomplete_field_init => gk.maps.autocomplete_field_init
  • 'gravitykitmapsinvalid_coordinates' => gk.maps.invalid_map_coordinates
  • gravitykit_maps_after_process_map_markers => gk.maps.after_process_map_markers
  • gravitykit_maps_beforeInit => gk.maps.before_maps_init
  • gravitykit_maps_afterInit => gk.maps.after_maps_init
  • gravitykit_maps_init_maps => gk.maps.init_maps
  • gravitykit_maps_before_init_map => gk.maps.before_init_map
  • gravitykit_maps_after_init_map => gk.maps.after_init_map
  • gravitykit_maps_before_process_map_markers => gk.maps.before_process_map_markers
  • gravitykit_maps_after_process_map_markers => gk.maps.after_process_map_markers
  • gravitykit_maps_getMaps => gk.maps.get_maps
  • gravitykit_maps_getSearchMaps => gk.maps.get_search_maps

• Improved: Accessibility of the temporary notice displayed during the executing of an Ajax request
• Fixed: Preview image for the "Business Map Listing" form preset in the View editor
• Fixed: Incorrect map centering when geolocation radius value is left empty during search
• Fixed: Incompatibility with some plugins/themes that use Laravel components
• Fixed: PHP warning messages that occurred under specific conditions
• Updated: Foundation to version 1.0.12

We’re so excited to announce the release of Maps 2.0. Read the Maps 2.0 announcement blog post. There are so many great new features:

• Geolocation radius search - Users can now search for entries within a certain radius of their current location or a specific location
• Draggable maps with "Redo search in map" and "Search as map moves" - Users can now search using the map itself! Map markers will refresh in real-time as you click and drag the map to different locations.
• Address field autocomplete - Make it easy for users to enter addresses using address autocomplete. Enable this feature by editing your form and checking the new “Enable geolocation autocomplete” checkbox in the settings of Address fields.

• Faster maps - We’ve rewritten our map rendering to dramatically improve performance

• Added: "International Autocomplete Filter" setting to restrict the countries that are used for address autocomplete

• Modified: Draggable maps functionality requires Views have REST API enabled
• Modified: The "Redo search in map" and "Search as map moves" settings are now enabled by default

Developer Updates:

• Added: Wrapping <div> surrounds each View, matching the containers in Table and List layouts
• Added: templates/search-field-geo_radius.php template file
• Added: Javascript hooks:
  • Filters:
    • gravitykit/maps/autocomplete_input_id Modify the input ID used for address autocomplete powered by Google Maps
  • Actions:
    • gravitykit/maps/autocomplete_field_init Allows third-party inclusion of actions on initializing the field for auto complete
• Added: PHP hooks:
  • Filters:
    • gk/gravitymaps/geolocation_fields - Filter which fields are considered geolocation fields
    • gravityview/view/wrapper_container - Modify the HTML wrapper container for the View; see examples of modifying the container
    • gk/gravitymaps/current_location_instant_search - Change the default setting for the Current Location behavior: true will instantly search when the current location is allowed by the browser and false requires users click the submit button (default: false)
• Modified:
  • templates/fields/entry_map.php template to fetch existing instance of object for improved performance
  • templates/map-header.php and templates/map-footer.php files to add the container wrapper (required for draggable maps)

Note: GravityView Maps now requires PHP 7.2 or newer

• Improved: Unrestricted Google Maps API key is now stored encrypted in the database and is partially masked when displayed in settings

• Fixed: PHP 8.1 notices
• Fixed: Fatal error on some hosts due to a conflict with one of the plugin dependencies (psr/log)
• Fixed: Address geocoding script being loaded on all admin pages

• Added: You can now use Drop Down and Radio Buttons field choices to set an entry's map marker icon—you can show different icons based on the submitted value of the fields! Learn more about choice-based marker icons.
  • A huge thanks to Jetsloth for letting us use their excellent Image Choices code as a base for this feature 🦥🤗
• Added: A "Link the Title" View setting to control whether the info box Title automatically links to the single entry page
• Improved: Optimize marker rendering on the map
• Improved: Updated the default map icon to be a vector graphic instead of an image
• Improved: Map zoom options now include some helper text to be clearer
• Fixed: Fatal error on some hosts that use weak security keys and salts

Developer Updates

• Modified: map-marker-infowindow.php template now uses link_open and link_close placeholders and the anchor tag is passed into the template. A reminder: you can use the gravityview/maps/infowindow/content/vars to modify the info box content.
• Modified: Markers in the GV_MAPS JavaScript object now pass an array for icon, instead of icon_url. This allows modifying the icon size, anchor, etc. before being rendered on the map.

• Fixed: Critical error when rendering map in the single entry View

• Improved: Reduced the plugin download package size

• Added: New WordPress admin menu where you can now centrally manage all your GravityKit product licenses and settings (learn more about the new GravityKit menu)
  • Go to the WordPress sidebar and check out the GravityKit menu!
  • We have automatically migrated your existing Google Maps API key, which was previously entered in the Views→Settings page
  • Request support using the "Grant Support Access" menu item
• Added: Maps settings are now available for network subsites in a multisite environment
• Added: Ability for the network administrator to share Google Maps API keys with all subsites
• Added: Ability to use a separate key for Geocoding that's never exposed to end users
• Updated: Prevent a potential error when using the Divi theme without a Google Maps API key set

• Updated: GravityView (the company) is now GravityKit
• Improved: Google Maps API error notices
• Fixed: Configuration notices were being shown when a search returned no results

• Fixed: License key input not working with Gravity Forms 2.6+

• Improved: Show a notice when the Maps layout hasn't been fully configured
• Fixed: Maps not displaying properly when using block themes (in WordPress 5.9+)
• Updated: Translations with best matches from similar locales (Spain Spanish and Mexican Spanish, for example)

• Tested with WordPress 5.9
• Fixed: Map icon not working when editing an entry via Gravity Forms

• Fixed: 1.7.3 release was causing a fatal error due to some missing files

• Fixed: Map not initializing when the View is embedded in a custom post type
• Updated translations: Dutch (thanks Erik!), Russian (thanks Irina!)

• Added: Support for Gravity Forms 2.5
• Updated: Map zoom level settings to include 19–21
• Fixed: Map not being initialized when the View shortcode is embedded via the Elementor page builder
• Fixed: Cached coordinates for multi-input fields would not clear when updating entries

Developer Updates:

• Added: Ability to center the map using the map options filter. See sample code here
• Added: gravityview/maps/marker/add filter to modify marker before it gets added to the map

• Updated: Polish translation (Thanks, Dariusz Zielonka!)
• Fixed: Locations not being updated when non-Address fields were used for coordinates
• Fixed: Google Maps API-checking script being loaded on all admin pages

• Improved: Allow input of latitude and longitude all the time for an Address field
• Improved: Many enhancements to the API key setup
  • Maps now will show a warning to administrators when the API settings aren't valid
  • Maps will now not show to users if the API isn't configured properly (instead of showing a broken map)
  • Added API key validation in the Maps section of the GravityView settings screen
  • Simplified settings by removing less-used methods of geocoding addresses (they are still available via developer filters)
  • Improved error message language
• Improved: Allow deleting geocoding results by saving empty latitude/longitude fields
• Changed: If an address only contains default values (such as Default State/Province or Default Country), do not show a marker on the map
• Fixed: Map Icon Picker field #97
• Fixed: JS console error in Chrome
• Fixed: When the Google Maps key isn't working for geocoding, it was preventing other providers from working
• Fixed: Address wasn't being properly formatted when passed to geocoding providers

• Fixed: Hide map when "Hide View data until search is performed" is enabled for a View
• Updated: Turkish translation (thanks, @suhakaralar!)

• Fixed: "Hide View data until search is performed" setting not working (also requires GravityView 2.2.1)
• Fixed: JavaScript error when map has no markers
• Updated translations - thank you, translators!
  • Polish translated by @dariusz.zielonka
  • Russian translated by @awsswa59

Developer Updates:

• Added: alt tag to default icon in Map Icon field
• Added: gravityview/maps/available_icons/sections and gravityview/maps/available_icons/icons filters to modify the icons shown in the Map Icon field
• Fixed: Add additional marker icons to the list in the Map Icon by adding .png images to your theme's ``/gravityview/mapicons/` subdirectory
• Fixed: Map Icon field compatibility with Gravity Forms 2.4 deprecation of conditional_logic_event()
• Modified: maps-body.php template file to run gv_container_class() on the .gv-map-entries container DIV

Learn all about this update on our blog post

• Added: Marker clustering—display multiple markers on a map as a single "cluster" Learn how
• Added: When multiple markers are at the same location, clicking the location expands to show all markers
• Added: You can now override coordinates for address fields Learn how
• Added: Support for multiple address fields for a single entry Here's how
• Improved: When geocoding fails for an address, a note is added to the entry
• Improved: Map Icon field scripts are only loaded when the field is present
• Improved: When an entry is updated, refresh the geocoding cache only if the address has changed
• Improvement: If an entry has no address, but the Gravity Forms field has defaults set, use the defaults for geocoding
• Fixed: Google Maps API key not being added properly
• Fixed: When site was in debug mode (WP_DEBUG was enabled), addresses would be re-geocoded on each page load
• Fixed: Map Icon field styles loaded on Gravity Forms Preview and Gravity Forms Edit Entry screens

• Fixed: Address fields with no label were appearing blank in the View settings dropdown
• Fixed: Standalone map fields not rendering
• Fixed: Address fields displaying multiple times on embedded Views
• Fixed: Error related to custom marker icons
• Fixed: Empty address field dropdown choice in View Settings when the field had no label
• Fixed: Maps scripts loading on all admin screens
• Tweak: Reduced number of database calls
• Changed: Hide the map widget when there are no results
• Changed: If GravityView core caching isn't available, don't cache markers
• Updated translations

• Updated: "Zoom Control" setting has been simplified to "None", "Small", or "Default"; this is because Google Maps no longer allows custom zoom control sizes
• Fixed: Don't render Maps widget if using a DataTables layout (we are hoping to support this in the future)
  • Also don't show Maps widget and fields in the Edit View screen when using a DataTables layout
• Fixed: Map not displaying when widget is in "Below Entries Widgets" zone
• Fixed: Javascript error when using the WordPress Customizer

Developer Notes:

• Allow global access to manipulate maps after instantiation (see example)
• Added ability to set mobile_breakpoint via the gravityview/maps/render/options filter
• zoomControlOptions no longer allows style value to be set; instead, only position is valid (See example)

• New: Configure info boxes to display additional information when clicking a map marker. Learn how here!
• Fixed: "Undefined index" PHP warning on frontend when saving a new Map View for the first time
• No longer in beta!

Developer Notes:

• Added: Filter gravityview/maps/field/icon_picker/button_text to modify the text of the Icon Picker button (Default: "Select Icon")
• Added: Use the gravityview/maps/marker/url hook to filter the marker single entry view link url
• Added: Use the gravityview/maps/render/options hook to change the marker link target attribute (markerlinktarget`). Read more

• Added: Option to set map zoom, separate from maximum and minimum zoom levels. Note: this will only affect Entry Map field maps or maps with a single marker.
• Fixed: Don't show a map if longitude or latitude is empty
• Fixed: If entry has an icon already set, show it as selected in the icon picker

• Fixed: Google Maps geocoding requires HTTPS connection
• Fixed: Support all WordPress HTTP connections, not just cURL
• Added: Custom filters to allow the usage of different fields containing the address value Read more
• Added: Filter to enable marker position based on the latitude and longitude stored in the form fields Read more
• Added: Entry Map field on the Multiple Entries view
• Added: How-to articles showing how to sign up for Google, Bing, and MapQuest API keys
• Fixed: Map layers not working for multiple maps on same page
• Fixed: GRAVITYVIEW_GOOGLEMAPS_KEY constant not properly set
• Fixed: Error when zoomControl disabled and zoomControlOptions not default
• Modified: Check whether other plugins or themes have registered a Google Maps script. If it exists, use it instead to avoid conflicts.
• Tweak: Update CSS to prevent icon picker from rendering until Select Icon button is clicked
• Tweak: Update Google Maps script URL from maps.google.com to maps.googleapis.com

• Added: Lots of map configuration options
  • Map Layers (traffic, transit, bike path options)
  • Minimum/Maximum Zoom
  • Zoom Control (none, small, large, let Google decide)
  • Draggable Map (on/off)
  • Double-click Zoom (on/off)
  • Scroll to Zoom (on/off)
  • Pan Control (on/off)
  • Street View (on/off)
  • Custom Map Styles (via SnazzyMaps.com
• Fixed: Single entry map not rendering properly
• Fixed: Reversed http and https logic for Google Maps script
• Fixed: Only attempt to geocode an address if the address exists (!)
• Fixed: Only render map if there are map markers to display
• Tweak: Added support for using longitude & latitude fields instead of an Address field learn how
• Tweak: Hide illogical field settings
• Tweak: Improved translation file fetching support

• Added: Ability to prevent the icon from bouncing on the map when hovering over an entry see sample code
• Modified: Set a maxZoom default of 16 so that maps on the single entry screen aren't too zoomed in
• Fixed: Map settings filtering out false values, which caused the gravityview/maps/render/options filter to not work properly
• Fixed: Map settings conflicting with Edit Entry feature for subscribers
• Fixed: Fatal error: Call to undefined method GFCommon::is_entry_detail_edit()
• Updated: French, Turkish, Hungarian, and Danish translations. Thanks to all the translators!

• Added: New Gravity Forms field type: Map Icon. You can choose different map markers per entry.
• Added: Middle field zone in View Configuration
• Tweak: Improved styling of the map using CSS
• Updated translations

• Fixed: Missing Geocoding library
• Updated translations

• Initial release