Use it now
Useful3 Signal4
Two managed settings can block plugin hooks entirely or allow only managed plugins.
What's wrong with this entry?
Anonymous. No account, no email.
disableAllHooksallowManagedHooksOnly--bare
What
Even with the rollout flag on, the loader filters which plugins may contribute hooks. Two managed settings keys control it: disableAllHooks blocks every plugin, and allowManagedHooksOnly restricts loading to managed plugins.
Details
- Running with --bare disables hooks entirely.
- When two plugins share a name, only the first loads: the managed one, or otherwise the one from the earlier source.
- Every exclusion is logged with the reason it was excluded.
Evidence
only managed plugins run (allowManagedHooksOnly / disableAllHooks)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Managed setting to block command-sourced plugins
Both mention disable hook allow managed only
-
v2.1.229
Plugins can be installed from a command that produces the plugin directory
Both mention disable hook allow managed only
-
v2.1.229
Marketplaces can ship a plugin built by running a local command
Both mention disable hook allow managed only