{"version":"2.1.282","anchor":"failed-plugin-removal-now-forces-uninstall-even-if-settings","canonical_anchor":"failed-plugin-removal-now-forces-uninstall-even-if-settings","heading":"Removing a plugin that failed to load now goes through even if settings still enable it","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/failed-plugin-removal-now-forces-uninstall-even-if-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Removing a plugin that failed to load now goes through even if settings still enable it\n\nIn `\/plugin`, removing a plugin that failed to load now uninstalls it even when settings still have it switched on\n\n**Unclear.** It is unclear what happened before when settings still enabled a failed plugin you tried to remove.\n\n**What**\n\nIn `\/plugin`, removing a plugin that failed to load now tells the uninstall step to remove it anyway, even if a settings file still has the plugin switched on. Where the plugin is installed (for example for your user or for a project) is now worked out in the same step.\n\n**Why**\n\nBroken plugins should be easier to get rid of.\n\n- Area: Plugins\n- Names: `\/plugin`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}