The Geocoder Field module stores forward-geocoding settings below a nested `geocode` key in field third-party configuration, but the configuration schema does not define that mapping.
This produces configuration schema warnings such as:
field.field.example.example_field:third_party_settings.geocoder_field.geocode missing schema
The missing schema affects the nested `field` and `delta_handling` values used by the Geocode operation.
Related historical issues #2954070, #2988543, and #2990876 addressed older Geocoder 2.x/3.x schema and configuration changes. They do not cover this current Geocoder 4.x nested mapping.
1. Install Geocoder 8.x-4.35 with the Geocoder Field submodule enabled.
2. Configure a field to use the “Geocode from an existing field” operation.
3. Save or export the field configuration.
4. Validate the active configuration schema.
The resulting configuration contains:
third_party_settings:
geocoder_field:
geocode:
field: ...
delta_handling: ...
The configuration schema reports that `third_party_settings.geocoder_field.geocode` is missing schema.
Add a schema definition for the nested `geocode` mapping in `modules/geocoder_field/config/schema/geocoder_field.schema.yml`, including:
- `geocode.field` as a string
- `geocode.delta_handling` as a string
The existing top-level `field` and `delta_handling` definitions should remain because they are used by the current field configuration structure and reverse-geocoding configuration.
- Add the missing nested `geocode` mapping to the configuration schema.
- Verify the schema against forward-geocoding field configurations.
- Verify that the complete Geocoder configuration schema validates without warnings.
None.
None.
None.
None. This only documents existing configuration.
Add the missing configuration schema for nested Geocoder Field geocoding settings.
AI assistance disclosure: This issue summary and proposed resolution were prepared with assistance from an AI tool and reviewed by the issue reporter.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | geocoder-schema-errors.png | 60.72 KB | nick hope |
| #4 | List of configuration data for field.field_.node_.geo_place.field_geofield | Drupal 11 Test.pdf | 174.08 KB | itamair |
| #4 | Configuration inspector | Drupal 11 Test.pdf | 125.4 KB | itamair |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
nick hope commentedComment #4
itamair commentedHi Nick ...
sorry I cannot reproduce your schema errors/warning.
As you suggest, I have a node (Geo Place) with a Simple Text Filed (String Address ) that holds the Address and a field_geofield that is geocoded from the "String Address".
No errors in my schema but just some not harmful warning says that the schema cannot be validated.
I attach here the Config Inspector output.
I don't get where is the real issue here.
Couldn't we co-live with all this? It looks totally un-harmful to me.
Comment #5
nick hope commentedHi Italo. I’ve attached a screengrab of the warning.
This is showing because I have Drupal’s standard local development services enabled on my local development site. The configuration schema checker therefore reports incomplete configuration schema as a warning when configuration is saved.
After rebuilding caches, the warning appears when saving a Geolocation field configuration that uses Geocoder Field’s reverse-geocoding settings. In my case, the warning identifies the following configuration path as lacking schema:
field.field.media.remote_video.field_geolocation:third_party_settings.geocoder_field.geocodeThe exact diagnostic is “missing schema”.
The affected field configuration contains:
The proposed change only adds schema for the existing `geocode` mapping (`field` and `delta_handling`). It does not change the geocoding behaviour or the stored configuration.
So, in practice, in my case the issue is cleaning up the warning rather than fixing a functional problem. However, completing the schema may help prevent configuration-validation or automated-test problems later.
Comment #6
itamair commentedOk, Nick I could reproduce your use case and your MR !86 looks cleaning the schema warning/error.
Let's merge ... (it shouldn't harm anything else).
Will be part of the next Drupal Geocoder release.
Thx!
Comment #7
itamair commented