| 开发者 | wonderfulplugins |
|---|---|
| 更新时间 | 2026年10月3日 02:44 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
wonderful-fatal-circuit-breaker folder to the /wp-content/plugins/ directory.E_ERROR, E_PARSE, E_CORE_ERROR, and E_COMPILE_ERROR — the errors that actually take a site down. Warnings, notices, and deprecations are ignored.
No. The threshold has a hard minimum of 2, and the default is 5 fatals within 10 minutes. A one-off hiccup never trips the breaker.
Nothing — they are never deactivated automatically. If a protected plugin keeps crashing, you receive a webhook notification (if configured) so you can act manually. This plugin itself is always protected.
No. It never deactivates itself, it never touches must-use plugins, and it only ever removes a plugin from the active plugins list — nothing is deleted, no files are written, and no drop-in is installed. Every deactivation can be undone with one click on the Plugins screen, and the admin notice tells you which plugin it was and why.
Only to the webhook URL you enter yourself — the plugin has no service of its own and contacts nothing else. Sent are the site address, the affected plugin slug, the error message, file and line, and the threshold that was reached. No visitor IP addresses, cookies, form contents or account data. Without a webhook URL nothing leaves your site at all. See "External services" above.
Runtime fatals — the vast majority, e.g. a plugin crashing while rendering a page — are caught. Fatals that happen while WordPress is still loading the plugin files themselves (e.g. a syntax error in a plugin's main file) occur before this plugin can register its handler and cannot be counted.
The breaker only manages the per-site active plugins. Network-activated plugins are never touched.
No. The plugin only runs a very lightweight check at the very end of a PHP process, and only if a fatal error has occurred. It has no impact on the performance during normal site operation.