Contrib.social

Enforced config registry in active config does not get removed when target module is uninstalled

Open on Drupal.org →
Created on 28 August 2022, over 2 years ago
Updated 12 January 2024, about 1 year ago

Problem/Motivation

Actually, it now seems to be uninstalled correctly when Config Enforce is uninstalled. Marking as works as designed, so it was likely caused by other changes during development. Will be re-opened if this comes up again.

Steps to reproduce

  1. Install Config Enforce Devel for the first time, so that it creates the default target module.
  2. Enforce one or more configs.
  3. Uninstall the default target module.
  4. Try to install the default target module; Drupal will refuse stating that the config object already exists.

Proposed resolution

Add the module as an enforced dependency to its registry in active config.

Remaining tasks

TBD.

User interface changes

None?

API changes

None?

Data model changes

See above.

🐛 Bug report
Status

Closed: works as designed

Version

1.0

Component

Code

Created by

🇨🇦Canada ambient.impact Toronto

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

Comments & Activities

Not all content is available!

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

  • Comment about 1 year ago →
    🇮🇹Italy kopeboy Milan

    How do you "Add the module as an enforced dependency to its registry in active config." ?!

    ie. how to fix the problem? I also can't re-enable a module that was the default target setting after uninstalling it (without first removing it as default target setting for config_enforce)

  • Comment about 1 year ago →
    🇨🇦Canada ergonlogic Montréal, Québec 🇨🇦

    @kopeboy You're commenting on a closed ticket. Please open new tickets in the future.

    The underlying problem seems to be that we allow the default target module to be disabled at all. That seems like a bug.

    See: 🐛 Disabling the default target module causes issues Active . It's a bit vague on the issues that this bug causes. @kopeboy could you please comment on that issue with the problem(s) you are seeing?

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024