{"version":"2.1.221","anchor":"batch-plugin-install-distinguishes-disabled-by-default-from-","canonical_anchor":"batch-plugin-install-distinguishes-disabled-by-default-from-","heading":"Batch plugin install distinguishes disabled-by-default from disabled-in-settings","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/batch-plugin-install-distinguishes-disabled-by-default-from-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Batch plugin install distinguishes disabled-by-default from disabled-in-settings\n\nBatch plugin installs now tell you which plugins are off by default versus off in your settings.\n\n**What**\n\nThe multi-plugin install summary tells you why each installed plugin is not running, and the closing line counts only the plugins that actually came up.\n\n**Details**\n\n- Two separate lists: \" Disabled by default \u2014 enable in \/plugin: \" for manifest defaults and \" Disabled in your settings: \" for the user's own settings.\n- The active count decides between \"Plugins are now active.\", \"Run \/reload-plugins to activate.\" and \" Some plugins couldn't be loaded \u2014 see \/plugin for details.\".\n- The single-plugin screen carries matching `installedDisabled` and `installedDisabledByDefault` view-state fields, derived from the `enabledPlugins` setting and `manifest.defaultEnabled`.\n\n**Evidence**\n\n` Disabled in your settings: `\n\n- Area: Plugins\n- Names: `\/plugin`, `\/reload-plugins`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}