| 开发者 | hatimm |
|---|---|
| 更新时间 | 2026年8月22日 17:39 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
WP_DEBUG_LOG), with a configurable threshold (default: 1).wp_mail() — no third-party email service required.vigilo-monitor folder to the /wp-content/plugins/ directory, or install the plugin directly through the WordPress admin under Plugins → Add New.wp-config.php to enable it:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
If logging isn't enabled, the dashboard widget and settings page will show this check as "unknown" rather than a false "0 errors".No. All checks run entirely on your own server. No data is sent anywhere except the alert email, which goes to the recipient address you configure, sent via your site's own wp_mail().
The SSL check connects to your site's own hostname (as returned by home_url()) on port 443. If your site doesn't serve HTTPS, or the check can't reach it (firewall, local/staging environment, etc.), the status will show as "unknown" rather than a false alert.
WP_DEBUG_LOG isn't enabled, so there's no log for the plugin to read. See the Installation section above for how to enable it.
Once a day, via WP-Cron. You can also click "Run Check Now" on the settings page to check immediately.
Not in this version. Vigilo Monitor is deliberately scoped to email alerts only, to stay lightweight and dependency-free.
No, this version monitors one site at a time, installed per-site. A multi-site aggregated dashboard is a possible future product, not part of this plugin.