| 开发者 | wonderfulplugins |
|---|---|
| 更新时间 | 2026年10月3日 02:46 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
wonderful-webhook-alerts folder to the /wp-content/plugins/ directory.A webhook URL is a special web address provided by services like Slack, Discord, or Zapier. When your WordPress site sends a message to this URL, the service receives it and can post it, for example, in a specific chat channel. You can get this URL from the settings of your chosen service.
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 error type, file, line and message, the method and path of the crashed request, and peak memory against the configured limit. No visitor IP addresses, cookies, form contents or account data. Because the crashed request's path is included, a query string carrying personal data would travel with it. See "External services" above.
It reads its settings once per request and holds back half a megabyte of memory, so it can still report if the request runs out. Beyond that it does nothing until a fatal error happens.
The plugin reports E_ERROR, E_PARSE, E_CORE_ERROR, E_COMPILE_ERROR, E_USER_ERROR, and E_RECOVERABLE_ERROR — the same set WordPress itself treats as fatal.
Yes, labelled separately. On an out-of-memory crash the file and line PHP reports are wherever the last allocation landed, not the cause — so the notification also carries peak memory, the configured limit and the crashed request.
No. An identical error — same message, file and line — is reported at most once every five minutes, so a fault that hits many requests at once still produces one notification.
Yes: wp-content/fatal-error-handler.php, WordPress' official drop-in. It has to run first — WordPress registers its own shutdown handler before plugins load, and by then the error can already have been replaced by a later one.
If another plugin already owns that file, it stays untouched and the settings page says so. Alerts keep working either way. The file is removed when you deactivate or delete the plugin.
Yes. The filter wonderful_webhook_alerts_pre_crash_dispatch receives ( null, $url, $body ) and replaces the built-in transport when it returns anything but null.
E_USER_ERROR and E_RECOVERABLE_ERROR are reported too — the set WordPress itself treats as fatal.wonderful_webhook_alerts_pre_crash_dispatch.