Allow to switch between content and config storage layers

Created on 18 March 2018, over 7 years ago

Updated 28 May 2025, about 2 months ago

This is just a rough idea so far.

Currently, I have the following observation:

Config entities are stored within the file system which promotes them being used as part of a development process via version control
Content entities are stored within the database which promotes them being used as part of editing processes directly on the website

This leads to situations where we have similar, competing modules with the differentiation based on their target user

The Contact module allows to create forms as config entities
The Webform module allows to create forms as content entities

In order to improve the situation, I'm proposing to evaluate if we could move allow to choose what should be stored as configuration on the file system and what should be stored as content within the database.

Suggested idea:

Entity types/bundles can define their default storage layer (database, configuration, ...)
Site administrators can override override the default storage layer by entity type/bundle

✨ Feature request

Status

Closed: works as designed

Component

Idea

Created by

🇨🇭Switzerland dasjo Zurich

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 2 months ago →
🇳🇿New Zealand quietone
I agree with @aaronmchale, that the premise of this issue isn't quite right. And since there hasn't been support for the idea in 4 years I am closing this issue.

If you are interested in this idea, open an issue in Drupal core. The Ideas project is being deprecated.
Comment about 2 months ago →
🇳🇿New Zealand quietone

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024