{"version":"2.1.246","anchor":"a-bad-plugin-config-no-longer-takes-the-plugin-down","canonical_anchor":"a-bad-plugin-config-no-longer-takes-the-plugin-down","heading":"A bad plugin config no longer takes the plugin down","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/a-bad-plugin-config-no-longer-takes-the-plugin-down","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### A bad plugin config no longer takes the plugin down\n\nA plugin with bad config now loads on defaults instead of failing, when enabled from trusted settings.\n\n**What**\n\nIf a plugin's options do not match the `userConfig` its plugin.json declares, and the plugin was enabled purely from trusted settings, it now loads on its default values with an error logged instead of failing. Plugins enabled any other way still throw as before.\n\n**Details**\n\n- Asking a plugin for options when its manifest declares no `userConfig` now logs a warning once per plugin, and every option reads as absent.\n\n**Evidence**\n\n`options requested but its manifest declares no userConfig; every option reads as absent`\n\n- Area: Plugins\n- Names: `userConfig`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}