Linux 软件免费装
Banner图

Beardo Multisite Activation Console

开发者 beardotools
更新时间 2026年9月28日 20:12
捐献地址: 去捐款
PHP版本: 8.0 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

network multisite plugins activation audit

下载

1.1.1 1.0.0 1.1.0

详情介绍:

Activate, deactivate, and manage plugins across every site in your network from one screen. Managing plugins on a multisite network is messy. Deactivating a plugin at the network level can leave it quietly running on individual sites — but how would you know? Finding out means clicking through site after site, and fixing it means holding your breath while a bulk action either works or takes the network down. Beardo Multisite Activation Console was built for one purpose: to save you that time. Every plugin, every site, one grid — with every change made carefully, recorded, and impossible to lock yourself out with. Activation Grid See the whole network at a glance: which plugins are network-active, which are switched on for individual sites, and which are off everywhere. Sort, search, and filter the way you already do in the WordPress admin — no spreadsheets, no site-hopping. Quick Change Change the status of any plugin on any site right from the grid. The console never fires off a giant batch and hopes for the best: each change runs on its own, with a health check first. If a plugin would break one subsite, that site is flagged and the rest of your network carries on untouched. Clear Stale Networks that have been around a while collect clutter — plugins marked active on a site and network-active at the same time. The console spots the redundant entries and clears them without deactivating anything that's genuinely in use. Dead References Deleted a plugin from the server but WordPress still thinks it's active somewhere? Those leftover entries hang around in your database for years. The console finds them and removes them. Logs Every change is written to a network-wide audit log: who did it, on which site, what they changed, and whether it worked. Filter by person, site, or plugin. When a client asks "who turned that off?", you'll have the answer in seconds. Need the log outside WordPress? Export it as a CSV or Excel (.xlsx) file straight from the Audit tab — either the filtered view you're looking at or the whole log — ready for a client report, a compliance review, or a spreadsheet. Guardrails A built-in protected list means the console will never deactivate itself, a drop-in, or anything else that would lock a super admin out mid-change. Developers can extend that list with a single filter. Feels like part of WordPress Built on the same DataViews interface WordPress itself uses, so there's nothing new to learn. It follows your admin color scheme, works in right-to-left languages, and looks like it belongs. Free, and nothing leaves your server No paid tier, no external services, no tracking, no phoning home. The plugin reads and writes only your own network's plugin state and its own audit log. Who it's for Requires a multisite network. Only super admins can use the console, and every request is protected by WordPress nonces and capability checks. Support & Documentation

安装:

  1. Upload the plugin folder to /wp-content/plugins/
  2. Network Activate it from Network Admin → Plugins
  3. Open Network Admin → Plugins → Activation Console
This plugin requires a WordPress multisite installation. It has no effect on single-site installs.

屏幕截图:

  • The audit log — who changed what, where, and when, filterable by person, site, or plugin

升级注意事项:

1.1.1 Security hardening release. No database changes; recommended for all users. 1.1.0 Adds CSV and Excel export of the audit log. No database changes; safe to update. 1.0.0 First public release.

常见问题:

Does this work on a regular (single-site) WordPress install?

No. The console is built for multisite networks and must be network activated. On a single-site install it does nothing.

Can it break my network by turning off something critical?

It's designed specifically so it can't. Changes run one at a time with a health check first, so a problem on one site stays on that site. And a protected list stops it from ever deactivating itself or anything that would lock a super admin out. Developers can add to that list with the beardo_mac_protected_plugins filter.

Who can use the console?

Only super admins (users with the manage_network_plugins capability). Regular site admins won't see it.

What does the audit log record?

Who made the change, which plugin, what they did, which site it applied to, whether it succeeded, and when. You can filter the log by person, site, or plugin.

Does it send any data anywhere?

No. There are no external calls, no analytics, and no tracking of any kind.

What happens if I uninstall it?

The audit log table is removed. Nothing else on your network is touched — your plugins stay exactly as they were.

更新日志:

1.1.1 1.1.0 1.0.0