{"version":"2.1.268","anchor":"new-wording-for-plugin-enable-confirmation-depends-on-a-chan","canonical_anchor":"new-wording-for-plugin-enable-confirmation-depends-on-a-chan","heading":"Plugin manager waits for pending toggles and clarifies when changes apply","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-wording-for-plugin-enable-confirmation-depends-on-a-chan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Plugin manager waits for pending toggles and clarifies when changes apply\n\nThe plugin manager now waits for enable\/disable actions to finish and tells you if changes apply immediately or need a reload\n\n**What**\n\n- Closing the plugin manager menu after toggling plugins used to show a static reminder message immediately. Now it tracks in-flight enable\/disable promises and, if any are still pending, waits for all of them to settle before returning to the menu, instead of firing the reminder text before the toggle finished.\n\n- The reminder text is now conditional on a new `changesApplyOnClose` flag: when set, plugin-enable confirmations say the change applies as soon as the menu closes; otherwise they still tell you to run `\/reload-plugins`.\n\n- The installed-plugins management screen now receives this `changesApplyOnClose` prop, wired to the same \"needs refresh\" state used for the reload prompt.\n\n**Why** This avoids showing a misleading confirmation before a plugin toggle has actually finished, and makes clear whether you need to run `\/reload-plugins` or the change already took effect.\n\n- Area: Plugins\n- Names: `\/reload-plugins`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}