Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
- install (success)
- uninstall (success)
- re-install (error)
Unable to install File Browser, embed.button.file_browser, image.style.file_entity_browser_thumbnail already exist in active configuration.
I need to delete both manually from config table to get to install again.
Comment | File | Size | Author |
---|---|---|---|
#16 | 2689585-16.patch | 1.84 KB | Sam152 |
#10 | clean_up_after_uninstall-2689585-10.patch | 820 bytes | jibran |
Comments
Comment #2
samuel.mortensonAre these bugs specific to File Browser or are all modules that provide this kind of config subject to this error? I'm wondering if this should be a core issue or closed in lieu of an existing core issue.
Comment #3
ksavoie CreditAttribution: ksavoie commentedI have un-/re-installed other modules without issue, but to be honest I have had this problem with a couple of modules in some capacity but many of the modules I am using are -dev as their are so few D8s that have production versions yet so I'm not surprised. I'm guessing that this issue is module specific and probably only because it's early -dev. I'm not overly worried about it as it does seem to function satisfactorily. I just wanted to get this on the list to be reviewed.
Comment #4
aspilicious CreditAttribution: aspilicious commentedThe image style config should have a dependency on the module (somewhere).
OR you can move the config to a folder names "optional".
Than it will be installed if it doesn't exist yet.
Comment #5
samuel.mortenson@aspilicious Ah, that makes sense. I would prefer the dependency as both of those pieces of config are (mostly) useless without File Browser. Thanks for the tip!
Comment #6
samuel.mortensonHere's a patch that adds those missing dependencies.
Comment #7
ChrisGrewe CreditAttribution: ChrisGrewe commentedI've had a similar problem with custom modules (and I just had this problem with File Browser too). The dependency may or may not be enough to get the config to remove itself properly. I've also taken to using hook_uninstall to clean up any configuration my module uses during the uninstall (suggestion came from elsewhere a few weeks ago, can't remember exactly where I read it first). For example, something like this:
With a similar line for each part of the configuration that needs to be uninstalled. That might help to mitigate these types of issues.
Comment #8
jibranThis is a correct fix.
Comment #9
jibranWe can keep this as well.
Comment #10
jibranI think it is ready now.
Comment #12
samuel.mortensonRan
drush si standard -y && drush en file_browser -y && drush pmu file_browser -y && drush en file_browser -y
, no errors! Thanks @jibran.Comment #13
jibranThanks @samuel.mortenson.
Comment #15
jibranCreated #2712669: Clean up after uninstall for content browser.
Comment #16
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedI believe this is actually the correct fix. The uninstall process will warn you config will be deleted this way.