No schema for solo.settings.

Created on 8 July 2025, 5 days ago

Problem/Motivation

After updating the theme from 1.0.20 to 1.0.22 and at the same time updating core from 11.1.8 to 11.2.2, I'm getting this warning:
"No schema for solo.settings. 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 the documentation โ†’ ."
I"m getting this warning too for my subtheme of solo.
I do not get this warning at D10 nor the previous D11.1. Probably there is a new feature in 11.2 that's more strict.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

๐Ÿ’ฌ Support request
Status

Active

Version

1.0

Component

User interface

Created by

๐Ÿ‡ง๐Ÿ‡ชBelgium ericvl

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @ericvl
  • ๐Ÿ‡ง๐Ÿ‡ชBelgium ericvl

    I forgot to tell that I'm getting this warning after I was saving the solo settings (or my subtheme). Sorry

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States flashwebcenter Austin TX

    Hello,

    Thank you for letting me know. Iโ€™ve added the solo.schema.yml file to the dev version.

    Please check on your end to see if you are still seeing the schema warning. If the warning persists, let me know the exact message so I can investigate and address it promptly.

    Best regards,
    Alaa

  • ๐Ÿ‡ง๐Ÿ‡ชBelgium ericvl

    Thank you Alaa for your quick response - as always.
    I'm getting this message now after I required the dev version with composer:

    Schema errors for solo.settings with the following errors: solo.settings:site_width_advertentie missing schema, solo.settings:site_width_event missing schema, solo.settings:site_width_fotoalbum missing schema, solo.settings:site_width_repetitie 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 the documentation โ†’ .

    I must say that advertentie, fotoalbum and repetitie are content types of me. I don't know if this is relevant.
    Thank you
    Eric

  • ๐Ÿ‡ง๐Ÿ‡ชBelgium ericvl

    Sorry, I forgot 1 contenttype. "event" is also a contenttype of mine. So, all four of my contenttypes gives an error. I don't know how to solve this. Maybe a wildchar could do the trick. I"m 75 and only knows something about assembler, pascal, C, C++ and java :-)
    You're the expert Alaa.
    Good luck and thank you again for your help.
    Greetings

  • ๐Ÿ‡บ๐Ÿ‡ธUnited States flashwebcenter Austin TX

    Hello Eric,

    Thank you for letting me know, and no worries at all.

    These schema warnings are harmless. They happen because your custom content types add keys that Drupalโ€™s schema system canโ€™t map dynamically, but they will not break your site.

    According to Drupal, mappings require all keys to be predefined, while sequences handle unknown keys. Since changing to a sequence would break other usersโ€™ configs, Iโ€™m keeping the safer mapping approach.

    You can safely ignore these warnings. Thank you again for your detailed note, and please let me know if you need anything else.

    Best wishes,
    Alaa

  • ๐Ÿ‡ง๐Ÿ‡ชBelgium ericvl

    Thank you, Alaa.
    If it doesn't hurt, I'm satified with this.
    Greetings and thanks for the great theme.
    Eric

Production build 0.71.5 2024