Problem/Motivation

I was evaluating this module and found that after I had uninstalled the module it did not remove the module's configuration.

Specifically the following config files were left behind after exporting the site's configuration.

  • field.storage.group_content.invitation_status.yml
  • field.storage.group_content.invitee_mail.yml
  • views.view.group_invitations.yml
  • views.view.my_invitations.yml

Steps to reproduce

  1. Install the module
  2. Clear Drupal cache (might not be needed)
  3. Export the site configuration.
  4. Confirm the modules configuration yaml files were created
  5. Uninstall the module
  6. Clear Drupal cache (might not be needed)
  7. The modules yaml configuration files are not removed

Issue fork ginvite-3201524

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

PCate created an issue. See original summary.

tunic’s picture

Status: Active » Postponed (maintainer needs more info)

Exported configuration files are managed by the Drupal Configuration Management System, not the module itself. Also, configuration files are not removed until you export the configuration again. I guess that if you export configuration after step 5 the configuration files would be removed. Please check this. However, I would say if they are not removed is not something related to this module but the configuration management system.

LOBsTerr made their first commit to this issue’s fork.

LOBsTerr’s picture

Status: Postponed (maintainer needs more info) » Needs review

@tunic you are right, that configuration is handled by Drupal config system, but we can force removal of the configs. I believe it is logical. I used the same approach for grequest module.

Please review and test https://git.drupalcode.org/project/ginvite/-/merge_requests/19

tunic’s picture

Issue tags: +ddd2022
tunic’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.