- Issue created by @ekes
- Status changed to Closed: duplicate
about 2 years ago 8:05pm 20 February 2023 - 🇮🇹Italy itamair
Hi @ekes. Why are you opening this geoPHP issue for the Geocoder module that doesn't depend from it?
May be this should be part of the Geofield module instead?Please keep in mind this already existing (and discussed) one:
https://www.drupal.org/project/geofield/issues/3245341 →
and this extended comment of mine:
https://www.drupal.org/project/geofield/issues/3245341#comment-14651742 →I tested further the
https://github.com/funiq/geoPHP
and it clearly breaks Geofield (and also Leaflet ... ) functionalities, that would hence need critical (and not regressive) adjustments.Basically the https://github.com/itamair/geoPHP gives us/me the possibility to quickly adjust itself to the potential future Drupa Geofield needs.
Its more recents progresses/commits (I pushed) nothing are than the adoptions/merge of issues/MRs raised in the https://github.com/phayes/geoPHP (abandoned) code base ...
and of course its triggering fix to this: https://www.drupal.org/project/geofield/issues/3294152 → - Status changed to Needs review
about 2 years ago 8:06pm 20 February 2023 - Status changed to Closed: duplicate
about 2 years ago 8:43am 21 February 2023 - 🇳🇱Netherlands ekes
Why are you opening this geoPHP issue for the Geocoder module that doesn't depend from it?
That'll be why I didn't find the existing issue! Too many tabs open in my brain.