- Issue created by @lo3001
- 🇮🇹Italy itamair
No evidence of this, that looks just assumption or wrong setup on your side.
The GeofieldMapSettingsForm constructor was created 7 years ago ... (and apparently never changed)
https://git.drupalcode.org/project/geofield_map/-/blame/11.0.x/src/Form/...Cannot replicate what you report, at all.
Suggestion: clear you drupal cache, if not yet done ... and (if not solved) eventually check what kind of override you are injecting on that Form setup / constructor.
Eventually, reopen and mark this as bug, ONLY if you have clear and objective evidence of the bug you found.
(just assumptions, sorry, are not enough). - 🇭🇰Hong Kong davidpetit
I am also encountering the same issue on a fresh Drupal 11 install, locally with DDEV.
- 🇫🇷France sneo
Hi, same here, fresh install of Dupal 11.
I wrote a fix for me.
- 🇮🇹Italy itamair
Yes, indeed I could reproduce this issue, after a clean Drupal 11 install, though pretty weird this doesn't happen in my existing Drupal 11 (and 10 site).
I could see that the GeofieldMapSettingsForm is not passing the needed second TypedConfigManagerInterface object to the ConfigFormBase parent object.Anyway I implemented a better fix (that the classical proposed in patch #4, thanks anyway for that) with this commit:
https://git.drupalcode.org/project/geofield_map/-/commit/969a7eb21104bca...
where the GeofieldMapSettingsForm is refactored to rely on the dependency injection container for adding new services instead of overriding the constructor (@see https://www.drupal.org/node/3076421 → )New releases of geofield_map ( 11.0.2 → and 3.0.24 → ) are solving all this ...