In ACF Pro 5.8.6 a change was made to the functionality of the map field. Now, when a marker is drag-and-dropped onto the map, the selected lat/lng are geolocated, and the marker will snap to the nearest address.
For the majority of use cases I imagine this is desirable. However I have a couple of clients who use the map field to indicate the meeting point for events in remote locations: think locations within states parks. This change has really messed them up, since the nearest address might be quite some distance from the desired meeting point.
I couldn’t see any way to disable the new “snap to address” functionality, so I am requesting that this be something that can be bypassed via a configuration setting, either in code or via ACF’s UI.
Just noticed the “Dev – Added “google_map_result” JS filter” on the 5.8.6 changelog. Is it possible to disable it? Our problem is that some locations must be defined by latitude and longitude coordinates instead of addresses as they are remote or non urban locations.
Thanks in advanced
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users