FatalGuard – PHP Error Log Viewer, Debug Log & Fatal Error Alerts
| 开发者 | zinodev |
|---|---|
| 更新时间 | 2026年10月31日 06:23 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
WP_DEBUG constants to wp-config.php (restoring your original values when you switch it off). And it is built to never brick your site: the fatal-error handler always falls back to WordPress's own recovery, with a file kill-switch and self-disarm sentinel as safety nets.
Free error log & debug log viewer, fatal error alerts & one-tap recovery
- Admin-bar log viewer — read your WordPress
debug.logand PHPerror_login a fast tabbed overlay with live tail, no FTP or SSH. - Grouped errors — repeated errors collapse into one entry with a count and last-seen, so the error that matters isn't buried in noise.
- Search & filter log entries to find the error that matters.
- One-switch file logging — FatalGuard writes the standard
WP_DEBUG_LOGconstants towp-config.phpfor you, and restores your originals when you switch it off. - Fatal error capture — catches the actual PHP fatal error behind the WordPress white screen / critical-error page and shows you the message, file and line.
- Instant Telegram error alert — get a message the moment a fatal error happens, with built-in anti-spam (dedupe, burst-cap and a circuit-breaker) so a fatal loop can never flood your phone. Telegram alerts are included in the free plugin.
- One-tap recovery — the fatal alert includes a signed link that deactivates only the crashing plugin and restores the site. It runs before regular plugins load, so it works even when wp-admin is down — no FTP, SSH or login needed. Nothing is deleted; re-enable the plugin when it's fixed.
- JavaScript error capture — front-end JS errors are logged in your admin session (requires the admin bar; visitor-side JS is not captured).
- Automatic secret redaction — database passwords, auth keys, API keys and tokens are scrubbed from your logs and alerts before they're ever shown or sent.
- Private, web-protected log storage — logs live in a hardened directory that can't be read from a browser, with non-guessable paths.
- Production-safe by design — full error detail only in development; on production your visitors always get WordPress's own recovery page, never a leak.
- Never-brick design — a self-installing, self-healing drop-in that always chains to WordPress's native recovery. A DISABLE kill-switch file is your no-SSH escape hatch.
- Status / diagnostics tab — see exactly what logging is on and where the log lives.
- Ask AI what's crashing your site — AI access (MCP). Connect Claude, Cursor, VS Code or any MCP client and just ask, in plain English: "What's the most recurring error this week?", "Which deprecations are in my active theme?", "What started failing after my last deploy?" The AI reads your real error history through FatalGuard's built-in, read-only MCP server — secured by a revocable API key, and nothing leaves your site except to the AI client you choose to connect.
- Searchable error history — every fatal kept in a database, grouped with counts and first/last-seen (free is live tail only). This history is what the AI reads.
- Multi-channel alerts — Slack, email, Discord and custom webhooks alongside Telegram.
- Multiple Telegram targets with per-site routing.
- Stealth mode — hide the plugin from other administrators.
- Weekly email digest of your site's errors.
安装:
- Upload the
fatalguardfolder to/wp-content/plugins/, or install FatalGuard from Plugins → Add New. - Activate the plugin. Fatal-error capture and alerts arm automatically; enable file logging with one switch under FatalGuard → General.
- Open the FatalGuard item in your admin bar to view logs.
- (Optional) Open FatalGuard and run the Telegram connect wizard: create a bot in @BotFather, paste its token, and press Start — FatalGuard detects your chat automatically, no chat-id hunting. Every fatal alert then includes the one-tap recovery link.
屏幕截图:
常见问题:
Why is my WordPress site showing a white screen or "There has been a critical error"?
That page hides a PHP fatal error. FatalGuard captures the real fatal error behind the white screen of death and shows you the message, file and line — and can send it to Telegram the instant it happens, with a one-tap link to recover the site by switching off the plugin that caused the critical error.
How do I read the WordPress debug log without FTP?
Install FatalGuard and open its admin-bar item. It shows your debug.log and PHP error_log in a searchable, tabbed viewer inside wp-admin — no FTP, SSH or cPanel needed.
Do I need to edit wp-config.php or turn on WP_DEBUG?
Not by hand. Flip the file-logging switch and FatalGuard writes the standard WP_DEBUG / WP_DEBUG_LOG constants to wp-config.php for you — pointing the log at its protected folder — and restores your original values when you switch it off. If wp-config.php isn't writable on your host, FatalGuard shows you the exact lines to paste.
Can this plugin break my site?
No. The fatal-error handler always falls back to WordPress's built-in recovery. If anything ever goes wrong, dropping a DISABLE file removes the handler — a recovery path that works even without SSH.
How do I get Telegram alerts for fatal errors?
Open FatalGuard and run the Telegram connect wizard: create a bot in @BotFather, paste its token, and press Start. FatalGuard detects your chat automatically and sends a non-blocking message whenever a fatal error is captured — no chat-id hunting.
My site is completely down and I can't log in — how do I fix it?
When a plugin fatals every page, wp-admin goes down too. Your FatalGuard fatal alert includes a secure recovery link: open it on your phone and tap once to deactivate the crashing plugin. It runs from a must-use loader that loads before regular plugins, so it works even when the rest of WordPress can't. Nothing is deleted — re-enable the plugin from Plugins once it's fixed.
Is the one-tap recovery link safe?
Yes. Each link is signed with your site's secret keys, does only one thing (deactivate the one named plugin), and expires after 4 hours. It's the same approach as WordPress core's Recovery Mode email link — a signed link stands in for the login you can't do while the site is down.
Does it support Slack, email or Discord alerts?
Slack, email, Discord and webhook alerts are part of FatalGuard Pro. Telegram is included free.
Can I use AI (Claude, Cursor) to debug my WordPress errors?
Yes — with FatalGuard Pro. Pro runs a built-in, read-only MCP server, so you can connect Claude, Cursor, VS Code or any MCP client and ask about your site in plain English: "what's the most recurring error this week?", "which deprecations are in my theme?", "what broke after my last deploy?" The AI reads your real captured error history; access is secured by a revocable API key, and nothing is sent anywhere except to the AI client you choose to connect.
Where are the logs stored?
In a private, web-protected directory with a non-guessable path — not the standard WordPress debug.log location. Browsers can't read the directory directly. The Status tab shows the exact path on your server.
How do I get notified when WordPress has a fatal error?
FatalGuard captures every PHP fatal error and sends an instant Telegram alert straight from the crashing request (free) — so you hear about a broken site before your visitors or client do. Pro adds Slack, email, Discord and webhook alerts, sent on the next successful page load.
What causes the WordPress white screen of death?
The white screen (or "There has been a critical error on this website") is almost always a PHP fatal error — a plugin/theme conflict, a memory limit, or bad code. FatalGuard captures the exact fatal error, file and line behind that screen so you can fix the real cause fast.
更新日志:
- Sturdier startup: optional log sources load only when their files are present, so a partial or customised install can no longer stop FatalGuard from loading.
- File logging and the show-errors toggle now use the standard WP_DEBUG constants: FatalGuard writes them to wp-config.php on your explicit toggle (backing up and restoring your original values) and WordPress core applies them — the plugin no longer changes any PHP setting at runtime.
- Out-of-memory fatals are now captured using pre-reserved memory instead of raising memory_limit.
- Recovery-screen styles delivered through the WordPress styles API; all dynamic output escaped at the point of output.
- Directory handling cleanup: plugin paths derived from the plugin's own location, uploads paths from wp_upload_dir().
- Log storage moved to a protected folder in the uploads directory; only the two files WordPress's architecture requires (the fatal-error handler and the recovery must-use loader) remain in wp-content.
- Runtime PHP error logging is now tied to the plugin's own logging state.
- Enqueue-based admin styles/scripts, hardened request-data handling, and readme/i18n housekeeping for WordPress.org standards.
- Webhook alerts now carry the one-tap recovery link.
- Log-viewer Alerts tab lists every alert channel with live status.
- Hardened request-data and file handling to meet WordPress.org coding standards.
- Settings: multi-field saves no longer return stale values - the save-sanitizer dedupe is now keyed per input, not a blanket once-per-request guard (B154).
- Settings: history retention now clamps to 0-3650 days at both ends.
- Hardened concurrency safety across fatal-capture, alert dispatch and log rotation — no duplicate or lost alerts under load.
- Expired recovery screens now offer a secure "Request a new recovery link" action (signature re-verified).
- Full localization: recovery screens + admin UI are now translatable, shipping with 10 languages (ES, FR, DE, PT-BR, IT, NL, RU, JA, ZH-CN, AR).
- Reliability fixes to delivery-failure tracking and Telegram/webhook health checks.
- Alert delivery now detects and surfaces failed Telegram/channel sends (previously dropped silently)
- New: daily silent Telegram health check validates the bot token + chat without posting, so a revoked token is surfaced within 24 hours
- Pro: conservative per-channel liveness checks for Slack, Discord and custom webhooks
- Dashboard widget now warns when an alert channel is failing instead of always showing "on"
- Initial release: admin-bar debug log & error log viewer, PHP error log reader, fatal error capture behind the white screen of death, one-tap recovery link to deactivate a crashing plugin and restore a down site, guided Telegram connect wizard with automatic chat detection, automatic file logging with no wp-config editing, never-brick self-installing drop-in, and free Telegram fatal error alerts.