Geocoder configuration form shows up on address field instead of on Geofield

Created on 11 February 2025, about 2 months ago

Problem/Motivation

When configuring a new content type with an address field and a geofield, the Geocoder configuration form shows up on address field instead of on Geofield.

Steps to reproduce

create content type with
- address field
- geofield

BUG: The option to enable geocoding shows up on the geofield - it should be on the address. (See also attached screenshot)

🐛 Bug report
Status

Active

Version

4.26

Component

User interface

Created by

🇩🇪Germany ducdebreme

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @ducdebreme
  • 🇮🇹Italy itamair

    hey ... @ducdebreme thanks for reporting this.
    BUT why do you assume this is a bug?
    Do you have clear evidence of that?
    Do you provide it ... ?
    Or do you simply feel things don't work as you expect?
    Well, that is not a clear bug ... but probably something that you missed or misunderstand.
    Please don't provide Issues marked as BUG, when you don't have (and provide) clear evidence of that.
    Rather create Support requests, that could be eventually turned into Bugs, when confirmed.

    Indeed in this case you are simply mislead.
    If the geocoder_address submodule is enabled, Address field can be indeed:
    be Geocoded from an existing field
    or Reverse Geocode from a Geofield type existing field.
    (as mentioned in your screenshot itself).

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024