Beardo Multisite Activation Console
| 开发者 | beardotools |
|---|---|
| 更新时间 | 2026年8月28日 02:03 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Activation matrix — every plugin's state (network active, active per site, or off) across all subsites in a single DataViews grid
- Safe transitions — one state change per request, so a fatal error on one subsite never takes down the whole batch
- Dry-run validation — backend health checks run before any change is executed
- Stale dual-state cleanup — detects plugins that are both network active and redundantly active per site, and strips the redundant entry without deactivating anything
- Audit log — every state transition is recorded network-wide with the acting user, target site, action, and result, filterable by user, site, and plugin
- Guardrails — a protected list stops the console from deactivating itself or a drop-in and locking a super admin out mid-operation
manage_network_plugins capability, protected by REST cookie authentication and nonces, and every posted value is validated against a server-side allowlist before anything runs.
Support & Documentation
- For support, visit help.beardo.tools
- Publisher site: beardo.tools
安装:
- Upload the plugin folder to
/wp-content/plugins/ - Network Activate it from Network Admin → Plugins
- Open Network Admin → Plugins → Activation Console
屏幕截图:
常见问题:
Does this work on a single-site WordPress install?
No. The console manages activation state across a multisite network, so it requires a multisite installation and must be network activated.
Can it break my network by deactivating something critical?
The console executes one transition per request so a fatal on one subsite is isolated, runs a backend dry-run before executing, and maintains a protected list (filterable via beardo_mac_protected_plugins) of plugins it will never touch — including itself.
Who can use the console?
Only super admins with the manage_network_plugins capability. Every REST request is nonce-protected and validated server-side.
What is recorded in the audit log?
Every state transition: the acting user, the plugin, the action, the scope, the target site, the result, and a timestamp. The log is stored in one network-wide table and can be filtered by user, site, and plugin.
What happens to my data if I uninstall?
Uninstalling removes the audit log table. No other data is created or modified.
更新日志:
- Initial public release.
- Activation matrix — every plugin's state (network active, per-site active, or off) across all subsites in a single DataViews grid
- Safe transitions — one state change per request, so a fatal error on one subsite never takes down the whole batch
- Dry-run validation — backend health checks run before any change is executed
- Stale dual-state cleanup — detects and strips redundant per-site entries for network-active plugins without deactivating anything
- Dead-reference cleanup — removes activation entries for plugins no longer present on disk
- Audit log — every state transition recorded network-wide with acting user, target site, action, and result, filterable by user, site, and plugin
- Guardrails — a filterable protected list (
beardo_mac_protected_plugins) prevents the console from deactivating itself or locking out a super admin - Admin theme compatibility — console colors flow through a plugin-scoped CSS token layer, and the focus ring follows the user's admin color scheme
- Full RTL support This release follows an internal beta series; 1.0.0 is the first version published to WordPress.org.