Group (content) Domain (config) relationship

Open on Drupal.org →

Created on 20 March 2023, over 1 year ago

Updated 5 June 2023, about 1 year ago

Problem/Motivation

Bringing in issues: https://www.drupal.org/project/3278349/issues/3293378 📌 Content Config relationship. Closed: duplicate and https://github.com/localgovdrupal/localgov_microsites/issues/371

It would be best if by default domain configuration, like its related group content, isn't exported or overridden on import if it's not there.

Optional ability to export would probably want to be tied to changing ids to something that would be guaranteed to match imported group content (UUIDs or something).

Proposed resolution

Implement ConfigEvents::STORAGE_TRANSFORM_IMPORT|EXPORT remove domain config matching groups on export, and maintain the db config on import.

📌 Task

Status

Version

3.0

Component

Code

Created by

🇳🇱Netherlands ekes

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @ekes
@ekes opened merge request.
Status changed to Needs review about 1 year ago1:48pm 1 April 2023
Comment about 1 year ago →
🇳🇱Netherlands ekes
Comment about 1 year ago →
🇬🇧United Kingdom Finn Lewis
I've tested this locally and it seems to do the trick.
Status changed to RTBC about 1 year ago12:09pm 31 May 2023
Comment about 1 year ago →
🇬🇧United Kingdom stephen-cox
I've also tested this and it works well.

Currently exported domain config is kept while the config for new sites is ignored.

Comment about 1 year ago →

ekes → committed a05b26d9 on 3.x

Issue #3349134 by ekes, Finn Lewis, stephen-cox: Group (content) Domain...

Comment about 1 year ago →
🇳🇱Netherlands ekes

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024