Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Decide on what issues need to be fixed before the 8.x-3.0-rc3 release of the Geolocation Field module for Drupal 8 in an effort to push this module to a full 8.x-3.0 release.
Comments
Comment #2
chris matthews commentedComment #3
chris matthews commentedI added some child issues that should be able to make the -rc3 release, but please feel free to add/remove as necessary. (I included the already committed issues just for clarity).
#3091087: Remove jQuery where unused
#3091474: Fix new CodingStandard warnings
#3091498: Add dynamic map support with blocks
#3091978: Add Traffic layer
#3092007: Unify simple JS based MapFeature
#3045426: Add address field widget
#3094126: Create an option to set Opacity for markers
#3095646: Add defaultTheme in tests extending BrowserTestBase.
#3095877: Missing schema definitions
#2956911: Geometry support
Comment #4
christianadamski commentedThanks!
The Geometry stuff is experimental and is only relevant in not to break all the other stuff.
The feature requests are irrelevant for this release as well for me.
What really sticks out is address handling and photon geocoder. Once these are done, we're good to go.
Comment #5
webberly commentedThere should be basic storage for formatted text addresses when using leaflet or other search.
Like suburb, county, state, country postcode.
It's not available in tokens data, considering the user gets all the data on their side when using a map widget it should store and make available in views etc.
Sometimes you have to make tables with the different address components.
https://www.drupal.org/project/geolocation/issues/3095316
Comment #6
chris matthews commented@ChristianAdamski, would you be able to go ahead and tag the -rc3 release to get a few important commits out of -dev. Especially, issue #3092054: How to geocode the address field ??
Comment #7
christianadamski commentedThere are still issues with address synchronisation
Comment #8
chris matthews commentedGotcha, is there an existing issue # to follow re: the outstanding bugs with address synchronization or is this something you'll just commit to -dev without an issue #?
Comment #9
christianadamski commented