- Issue created by @ericvl
- ๐ง๐ชBelgium ericvl
This could maybe a clue. ๐ Update core to Drupal 11.2.x and resolve schema issues triggered by settings.local.php Active
- ๐ง๐ช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