{"version":"2.1.246","anchor":"disabling-all-plugins-now-also-covers-plugins-that-were-enab","canonical_anchor":"disabling-all-plugins-now-also-covers-plugins-that-were-enab","heading":"Disabling all plugins now also covers plugins that were enabled without a settings record","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/disabling-all-plugins-now-also-covers-plugins-that-were-enab","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Disabling all plugins now also covers plugins that were enabled without a settings record\n\nDisabling all plugins now catches ones that had no settings entry and previously survived.\n\n**What**\n\nThe bulk disable path now gathers plugin sources from the live enabled list as well as from settings, so a plugin enabled from a source with no settings entry is written out as disabled instead of surviving the sweep.\n\n**Details**\n\n- Trusted sources are checked against a restricted record set before being written.\n- With nothing enabled the path still reports \"No enabled plugins to disable\".\n\n**Evidence**\n\n`No enabled plugins to disable`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}