Problem/Motivation

When using Onomasticon 2.2.4 on Drupal 11, enabling the Onomasticon filter on a text format and attempting to save the text format results in configuration validation errors such as "'onomasticon_xxx' is not a supported key."

The project page indicates that Onomasticon 2.2.4 is compatible with Drupal 11.

Environment:
- Drupal 11.3.10
- Onomasticon 2.2.4

Steps to reproduce

  1. Install Onomasticon 2.2.4 on Drupal 11
  2. Go to Configuration > Content authoring > Text formats and editors
  3. Edit an existing text format or create a new one using CKEditor5
  4. Enable the Onomasticon filter
  5. Attempt to save the text format

Comments

sarav9 created an issue. See original summary.

sarav9’s picture

sarav9 commented
Priority: Normal » Major
Issue summary: View changes
Issue tags: -schema, -validation
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 2.2.4 » 2.3.x-dev
dkmishra’s picture

dkmishra commented

Confirmed — reproduced this exactly on a local Drupal 11 install with Onomasticon 2.2.4. Enabling the filter and saving the text format at admin/config/content/formats/add throws "is not a supported key" for all 11 settings keys.

'onomasticon_vocabulary' is not a supported key.
'onomasticon_definition_field' is not a supported key.
'onomasticon_definition_filters' is not a supported key.
'onomasticon_tag' is not a supported key.
'onomasticon_disabled' is not a supported key.
'onomasticon_implement' is not a supported key.
'onomasticon_orientation' is not a supported key.
'onomasticon_cursor' is not a supported key.
'onomasticon_ignorecase' is not a supported key.
'onomasticon_repetition' is not a supported key.
'onomasticon_termlink' is not a supported key.

Root cause: the 2.2.4 release doesn't ship a config/schema/onomasticon.schema.yml

Without a schema, Drupal 11's stricter config validation rejects every key on save. This was already fixed for #3459880, and the fix is present on 2.3.x-dev.

Try patch https://www.drupal.org/files/issues/2024-07-08/compat-10.3-missing-schem... that will fix just the schema addition to the 2.2.4 codebase.