geocoder is geocoding from a field it is not requested to geocode from

Created on 27 April 2025, about 2 months ago

Problem/Motivation

On my custom facility entity, I have a geofield field_location and an address field field_address. field_location geocodes from field_address and field_address reverse geocodes from field_location. But I also have a plain text field field_name which I want to use as a pure label, and if I have that filled in then field_location geocodes from it, then field_address reverse geocodes from field_location, and the content I actually entered into one or both of those fields is lost.

Steps to reproduce

Set up as above. I used ECK.

Proposed resolution

Stop it from doing that :)

🐛 Bug report

Status

Active

Version

4.28

Component

Code

Created by

🇺🇸United States hyperlogos

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @hyperlogos
Comment 15 days ago →
🇮🇹Italy itamair
The use case described in this issue is very confused and also looks controversial to me.
Thus it looks that you have (in your configuration) the field_location that is both being geocoded by/from the field_address and the plain text field field. How could it be possible?
The actual Geocoder module doesn't support that (you can only geocode from 1 existing field, no more ...).
Please provide a better description (and a feasible version) of your complicate setup OR make it more feasible.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024