Configuration per content type / bundle

Created on 18 May 2024, 6 months ago

Problem/Motivation

Currently this module provides a global configuration, across all content end entity types. Since there will be differences between bundles in terms of what fields are available, it would be ideal if individual bundles could override the global settings.

Proposed resolution

Add a vertical tab to bundles, with configuration options:

  • A toggle for whether or not to override the global options (defaults to off)
  • If the override toggle is enabled, provide a copy of the global configuration form. I'm not sure we need to provide every option (it seems like it's more likely the need would be to just override a subset), but I'm inclined to follow the metatag model and just make all the fields available

Obviously, the code would need to be updated to check for bundle-specific configuration, and use that if available. Also, it will be necessary to create schema for the per-bundle configuration.

Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇨🇦Canada mandclu

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

Comments & Activities

  • Issue created by @mandclu
  • 🇨🇦Canada mandclu

    Another potential approach would be allowing the module to define profile/templates, and then those could either be associated to bundles (similar to workflows) or potentially specified as part of the token.

  • 🇨🇦Canada mandclu

    The more I think about this, the more I think that profiles as configuration entities is the best approach. In particular, these could be fieldable entities, which could be an easy way to address issues like Allow for a foreground image element Active , and then using this module with something like Field Token Value would open up all kinds of possibilities. I'm not sure if it would be possible to integrate with Field Group as a way to allow for simple layout options, but it would be worth exploring.

Production build 0.71.5 2024