Contrib.social

Ability to store the settings in the Drupal Configuration as Config Entity

Open on Drupal.org →
Created on 25 March 2025, about 1 month ago

Problem/Motivation

Now the module provides the ability to store the configured settings in the database as content entities - that's good. But in some cases, we want to store some settings as Drupal Configuration instead of content (we can exclude them from syncing using Config Ignore).

To cover this case, would be great to add the ability to choose the storage type for each Site Settings type - content or config. Is it hard to implement?

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

🇦🇲Armenia murz Yerevan, Armenia

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

Comments & Activities

  • Issue created by @murz
  • Comment about 1 month ago →
    🇬🇧United Kingdom scott_euser

    Yeah it's quite hard to do. I think you can use default content module perhaps (there may be other similar that convert content to config).

  • Comment about 1 month ago →
    🇦🇲Armenia murz Yerevan, Armenia

    Thanks for the feedback! Looked a bit into it already, and seems it is not very hard to implement.

    We should introduce a new Entity Type based on the ConfigEntityBase instead of the ContentEntityBase, and seems that's it. All entities, created with this Entity Type, will be stored in the configuration. I will try to implement a proof of concept for this.

  • Comment about 1 month ago →
    🇬🇧United Kingdom scott_euser

    That's not the hard part though, the hard part is the upgrade path. Would have to batch bulk convert, update all existing code, twig functions, test coverage, etc, probably require and configure Config Ignore to maintain the status quo.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024