Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
The configuration schema for the Glossify module’s settings is not correctly registered
in the system for later versions of Drupal (ie, 10.3+) which now validates configuration schema.
This issue prevents proper validation and recognition of configuration settings leading to errors such as "missing schema" or "missing keys" during Drupal updates. This also prevents resaving any Text Format that uses Glossify.
Steps to reproduce
- Upgrade Drupal to version 10.3.0
- Save the configuration for the Full HTML text format or any configuration form where Glossify settings are used.
Proposed resolution
Update the config schema file (glossify_taxonomy.schema.yml and glossify_node.schema.yml) as per https://www.drupal.org/node/3419181
Issue fork glossify-3457599
Show commands
Start 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
ewehbe commentedComment #4
ewehbe commentedComment #5
scott_euser commentedAccording to https://www.drupal.org/node/3419181 the type should be 'mapping' not 'filter' as well.
Comment #6
scott_euser commentedComment #7
scott_euser commentedOtherwise this looks good now, but I won't change to RTBC myself since I made a change here. If someone else could please do a final review. Thanks!
Comment #8
ewehbe commentedI have tested the changes, the module works as expected.
I will change the status to RTBC.
Comment #10
anybodyGreat work, thank you both!! Merging!
Comment #12
anybodyI'll tag a new release with this fix!