{"version":"2.1.246","anchor":"clearer-reason-when-an-administrator-has-blocked-plugin-hook","canonical_anchor":"clearer-reason-when-an-administrator-has-blocked-plugin-hook","heading":"Clearer reason when an administrator has blocked plugin hooks","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/clearer-reason-when-an-administrator-has-blocked-plugin-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Clearer reason when an administrator has blocked plugin hooks\n\nWhen managed settings block plugin hooks, the message now says that explicitly.\n\n**What**\n\nWhen plugin hook modules are refused because managed settings only permit hooks from enterprise-managed sources, the message now says so explicitly instead of reusing a generic reason.\n\n**Details**\n\n- Sits alongside the existing reasons for `--bare` and `disableAllHooks`.\n- Driven by the `allowManagedHooksOnly` and `disableAllHooks` settings; no other gate.\n\n**Evidence**\n\n`an admin stood the guard down (safe mode \/ managed allowManagedHooksOnly)`\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}