Error: Unable to re-install due to existing active configuration

Open on Drupal.org →

Created on 7 March 2024, 4 months ago

Updated 8 March 2024, 4 months ago

Problem/Motivation

After uninstalling this module, if you install this module again, then you will come across the error said,

Unable to install Gutenberg Editor, core.entity_form_display.taxonomy_term.pattern_categories.default, core.entity_view_display.taxonomy_term.pattern_categories.default, field.storage.block_content.field_pattern_category, field.storage.block_content.field_pattern_sync_status, taxonomy.vocabulary.pattern_categories already exist in active configuration.

Steps to reproduce

Install this module.
Delete the 'Gutenberg Blocks text format' filter as it blocks the uninstallation of this module.
Uninstall this module.
Install this module again.
At this stage, the error occured.

Proposed resolution

A similar fix for https://www.drupal.org/project/gutenberg/issues/3015328 →

Remaining tasks

PHPUnit test for installing this module.

User interface changes

N/A

API changes

N/A

Data model changes

N/A

🐛 Bug report

Status

Needs review

Version

3.0

Component

Code

Created by

🇦🇺Australia Mingsong 🇦🇺

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Merge Requests

!117Error: Unable to re-install due to existing active configuration
Open
🇦🇺Australia Mingsong
updated about 1 month ago

Comments & Activities

Issue created by @Mingsong
Merge request !117Issue #3426261 by @mingsong: Error: Unable to re-install due to existing active configuration → (Open) created by Mingsong
Status changed to Needs review 4 months ago7:40am 7 March 2024
Comment 4 months ago →
🇦🇺Australia Mingsong 🇦🇺
MR is ready for review.
Pipeline finished with Success
4 months ago
Total: 353s
#113520
Comment 4 months ago →
codebymikey
Looks good to me, but a couple feedback:

dependencies: + enforced: + module: + - gutenberg + module: + - gutenberg
I don't think the module dependency is necessary, as it'll probably be deleted once the dependencies are recalculated the next time the config is resaved.

I also believe according to the config schema order, the enforced key needs to be the last dependency entry:
Reference:

https://git.drupalcode.org/project/drupal/-/blob/9c1e1035/core/lib/Drupa...

https://git.drupalcode.org/project/drupal/-/blob/9c1e1035/core/config/sc...

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024