Problem/Motivation

Some elements saved in the module’s configuration object are not defined in the configuration schema. This triggers a warning during config export/import and in other operations that validate schema.

Schema errors for orejime.settings with the following errors:
orejime.settings:request_path missing schema,
orejime.settings:logo missing schema,
orejime.settings:implicit_consent missing schema,
orejime.settings:color missing schema.
These errors mean there is configuration that does not comply with its schema. This is not a fatal error, but it is recommended to fix these issues. For more information on configuration schemas, check out <a href="https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-schemametadata">the documentation</a>.

Steps to reproduce

  1. Enable the module.
  2. Open the module’s admin form in the back office and save the configuration.
  3. Export configuration (e.g., via the UI or drush cex).

The warning may also appear later during a configuration re-import (drush cim), when enabling another module (e.g., drush en some_module), or when saving configuration again in the back office.

Proposed resolution

  • Add missing keys to the configuration schema:
    • request_path
    • logo
    • color
  • Remove the implicit_consent element, as it appears to no longer exist / be used.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork orejime-3541992

Command icon 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:

About issue forks

Comments

johnatas created an issue. See original summary.

johnatas opened merge request !15

johnatas’s picture

johnatas commented

I also just noticed that the mapping for name, apps, and weight is missing in the category sequence.

I’m adding a new commit to include this mapping, as well as proper type handling for apps and weight in the config form submit.

johnatas’s picture

johnatas commented
Issue summary: View changes
johnatas’s picture

johnatas commented
Status: Active » Needs review
dhruv.mittal’s picture

dhruv.mittal commented

Reviewing it

dhruv.mittal’s picture

dhruv.mittal commented
Status: Needs review » Reviewed & tested by the community

I can confirm this issue persists with provided steps to reproduce
and patch is able to resolve the issue.
Thanks for your contribution @johnatas
Moving it to RTBC

fabsgugu’s picture

fabsgugu commented

Thanks for the correction !

I've merged.

fabsgugu’s picture

fabsgugu commented
Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

johnatas’s picture

johnatas commented

Thanks @fabsgugu for the merge.
Do you plan a new release soon with these changes?

Also, please don’t forget the credits ;)

Status: Fixed » Closed (fixed)

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