Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
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
- Install the module
- Clear Drupal cache (might not be needed)
- Export the site configuration.
- Confirm the modules configuration yaml files were created
- Uninstall the module
- Clear Drupal cache (might not be needed)
- The modules yaml configuration files are not removed
Issue fork ginvite-3201524
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:
Comments
Comment #2
tunicExported 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.
Comment #5
LOBsTerr CreditAttribution: LOBsTerr at European Commission and European Union Institutions, Agencies and Bodies commented@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
Comment #6
tunicComment #7
tunic