Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.We already have everything in place to simply add a map-based address field widget. So just do that.
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | 3045426-19-address-widget.patch | 3.25 KB | christianadamski |
| #3 | 3045426-3-address-field-widget-wip.patch | 3.18 KB | christianadamski |
Comments
Comment #2
christianadamski commentedComment #3
christianadamski commentedWIP
Comment #4
socialnicheguru commentedWill this connect an address field to geolocation or is this a replacement for it?
Comment #5
chris matthews commentedComment #6
christianadamski commentedNo, this is really just a formatter for address. As it has to geocode for every view, this should only be used in very specific cases,
Comment #7
webberly commentedIt should only do geocoder once when saving and store information
Comment #8
christianadamski commented@webberly What you describe is happening with the sync of geolocation field and address field. This is already implemented.
This ticket is specifically not for storing address data.
Comment #9
webberly commented@christianadamski address field only works with Google, I use geolocation/leaflet because it doesn't use Google.
I think the address/locality formatter shouldn't be dependant on data from Google only.
Comment #10
christianadamski commented@webberly, you might want to spent a bit more time on the different elements of geolocation.
There is a process to sync an address field and a geolocation field with each other, so that Google only has to be asked once.
This issue is about a pure formatter for address.
Comment #11
socialnicheguru commented@ChristianAdamski what is the process for syncing? I am currently using geocode, geolocation, address. Can I now only use address and geolocation?
Comment #12
christianadamski commented@SocialNicheGuru yes. Enable the geolocation_address and then enable Address synchronisation in the field widget form settings.
Please provide feedback.
Comment #13
chris matthews commented@ChristianAdamski, so the geofield module is not required, correct?
If so, the documentation is out-of-date.
Comment #14
christianadamski commentedHey, I didn't write those instructions.
I guess they work too, but based on the backend focussed geocoder module workflow.
Geolocation offers a completely different frontend based workflow to sync address module field.
Comment #15
christianadamski commentedNext steps:
- split up /modules/geolocation_address/js/geolocation-address-map-widget.js into 2 files
-- one API files
-- one file using the API for the address synchronisation
- use API in a new widget js for this issue
Comment #16
mowens commentedSaw some improvements on geocoder and it's working better.
Only remaining issue I see is that administrativeArea is not parsing the state properly. So the state dropdown will continue to be broken when using the address sync.
In this file:
/geolocation/modules/geolocation_address/src/Controller/GeocoderController.php
I had to modify the
public function reverse(Request $request) {geocoder function to parse the administrativeArea from $address['string'] but would be better to parse a component returned from the API.
Comment #17
rithesh bk commentedcurrently working on this issue .......
Comment #18
rithesh bk commentedComment #19
christianadamski commentedNon functioning WIP
Comment #20
christianadamski commentedThis got added at some point to 4.x