Linux 软件免费装

Wonderful Webhook Alerts

开发者 wonderfulplugins
更新时间 2026年10月3日 02:46
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv3
版权网址: 版权信息

标签

debug notification monitoring webhook fatal error

下载

1.2.0 1.1.0 1.1.1 1.0.0 1.2.1

详情介绍:

https://www.youtube.com/watch?v=xSWJNLhodK8 This plugin provides a simple but powerful function for developers and site administrators. It automatically captures critical PHP errors (fatal errors, parse errors, etc.) that would otherwise take your site down silently. Instead of having to check server logs, you receive an instant notification via a webhook to a service of your choice, like Slack or Discord. This allows for immediate action and faster debugging. The setup is minimal: just add your webhook URL on the settings page, and the plugin takes care of the rest.

安装:

  1. Upload the wonderful-webhook-alerts folder to the /wp-content/plugins/ directory.
  2. Activate the plugin through the 'Plugins' menu in WordPress.
  3. Go to Settings > Webhook Alerts in your admin dashboard.
  4. Enter your webhook URL and save the settings.
  5. Use the Send test message button to verify the connection. That's it!

常见问题:

What is a webhook URL?

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.

What data leaves my site, and where does it go?

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.

Does this plugin affect my site's performance?

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.

Which error types are reported?

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.

Does it also report "Allowed memory size exhausted"?

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.

The same error keeps happening. Will I get flooded?

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.

Does the plugin add a file to wp-content?

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.

Can I intercept the notification?

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.

更新日志:

1.2.1 1.2.0 1.1.1 1.1.0 1.0.0