A new field type for Advanced Custom Fields (ACF) that allows you to place multiple markers and choose multiple locations all on a single map field, resulting in a cleaner admin UI, better user experience for the CMS user and fewer Google Map API loads. The field will display the address for each map marker below the map so it’s even more manageable.
This field type solves the problem of only being able to select one location with the standard ACF Google Map field.
To choose multiple locations, you’d normally be required to use a repeater field with a Google Map field in it. This can quickly become chaotic and difficult to keep track of/manage.
This ACF field type is compatible with:
* ACF 5
On the new Google Maps (Multiple Markers) field, you can:
– LEFT CLICK on the map to place a new marker
– RIGHT CLICK on a marker to remove it
– CLICK AND DRAG a marker around on the map
– SEARCH for a place or address in the search box
– HOVER over an address in the address list below the map to see which pin it corresponds to
– LEFT CLICK on the trash icon on a row in the address list to remove it’s corresponding marker.
Google Maps API
Your Google Maps API key will need the following APIs enabled:
– Geocoding API
– Places API
- Copy the
acf-google-map-multifolder into your
- Activate the Google Map (Multiple Markers) plugin via the plugins admin page
- Register your Google Maps API key in your theme by following the instructions here: https://www.advancedcustomfields.com/resources/google-map/#requirements
- Create a new field in ACF and select the Google Map (Multiple Markers) type under the jQuery category
Contributors and Developers
“ACF: Google Maps Field (Multiple Markers)” is open source software. The following people have contributed to this plugin.Contributors
Interested in development?
- Initial Release.
- Updated readme.
- Tested with newest version of WordPress.
- Fixed bug where the field value wouldn’t properly reset when adding a new marker.
- Changed name from “Google Map” to “Google Maps”
- Bumped WordPress tested version to 5.9
- Adjusted text in readme.txt
- JS set to strict mode with “use strict”;
- Retested with WordPress 6.0