| 开发者 | sdobreff |
|---|---|
| 更新时间 | 2026年3月9日 21:39 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
wp_remote_* calls made by WordPress core, themes, and
plugins. Records URL, method, status code, response time, triggering plugin,
user, and full request/response detail. Export to CSV for external analysis.
Advanced filtering by domain, plugin, status, and date range.
Mail Logger & Composer
Records every email sent through wp_mail() — including headers, body,
attachments, CC, and BCC — and stores it in a searchable log. View the
rendered email body, resend any logged email, or compose and send new emails
directly from the admin. Supports HTML and plain-text previews.
SMTP Configuration
Configure custom SMTP settings (host, port, encryption, username, password)
with a built-in test email tool. Optionally log SMTP debug output to the
WordPress debug log.
WP Hooks Monitor
Define which WordPress actions and filters (core or custom) you want to
observe. The Hooks Capture module records each invocation with its parameters,
return value (for filters), and a full stack backtrace. Organise monitoring
rules into named groups, enable/disable per hook, and review the captured
output in a dedicated list view.
DB Table Manager
Browse, search, edit, and delete records across any table in your
WordPress database — including custom plugin tables. Displays table size,
engine, collation, row count, and schema information. Supports full and
filtered truncation and table drop with confirmation.
Server Info & System Status
Displays real-time server metrics (CPU load, memory usage, disk space,
PHP version, active extensions) as both admin-bar badges and a dashboard
widget. Also provides a detailed environment report useful for support tickets
and deployment checks.
Plugin Version Switcher
Roll back or switch between any previously downloaded version of an installed
plugin without leaving the admin. Useful for quickly reverting after a bad
update. Supports only free plugins from the WordPress repo.
Code Snippets
Write, save, and execute custom PHP snippets from the admin. Snippets support
shortcodes, can be enabled/disabled individually, and are sandboxed before
execution. Useful for one-off data migrations, testing custom logic, or
generating dynamic output without creating a custom plugin.
Recovery Mode
Generate single-use recovery links that can disable a specific plugin or
trigger a custom action — delivered via Slack, Telegram, or any configured
webhook channel. Designed for emergency recovery when the site is inaccessible
through normal means. The recovery URLs are sent in Slack and Telegram channels for security.
Other Features
0-day-analytics folder into /wp-content/plugins/ (or install
via the Plugins screen or WP CLI).Reading only the tail of the log avoids loading gigabytes of data into memory on every page view. The number of lines to read is adjustable via Screen Options on the Error Log screen.
Pagination would require seeking to arbitrary byte offsets in potentially very large files on every page load. The tail-read approach is orders of magnitude faster for the most common use case (seeing recent errors).
Go to 0 Day → Settings → Error Log and toggle "WP Debug Log Enabled". For best results, test the setting on a staging environment first.
Yes. In Settings → Error Log, click "Generate WP Debug Log File Name". A
cryptographically random filename will be written into wp-config.php,
making the log URL unguessable from the outside.
Most modules work correctly on multisite. The Recovery Mode feature has known limitations related to WordPress core multisite behaviour — use with caution and test on staging first.
No data is sent to any third-party service by the plugin itself. The Google PageSpeed integration only fires when you explicitly click "Run PageSpeed Analysis" and requires you to supply your own Google API key. Slack and Telegram are opt-in notification channels for Recovery Mode.
Go to Settings and enter your Google PageSpeed Insights API key (free from Google Cloud Console). You can then analyse any URL from Performance → PageSpeed or from the Performance → URLs tab.
It runs 32+ automated checks including: PHP version currency, WordPress core version, SSL certificate validity, WP_DEBUG exposure, file permissions, database table prefix security, XML-RPC status, login URL predictability, autoloaded options size, active plugin bloat, caching configuration, gzip compression, lazy loading, image optimisation, cron health, and more. Each check is scored and colour-coded with a recommended action.
The Error Log module reads your flat PHP error log file. The Fatal Error Tracker stores fatal errors in a dedicated database table that persists across log rotations and file truncations. Use both in combination: the log for real-time detail, the tracker for long-term history. It will capture / store PHP errors even if WP_DEBUG is disabled, this way you will always be aware if something is wrong.
Yes. Go to Hooks Monitor and add a new monitoring rule specifying the hook name (action or filter). From that point on, every invocation is recorded with its arguments, return value, and full PHP backtrace. Rules can be grouped, toggled, and removed without any code changes.
Go to Snippets, create a new snippet, write valid PHP, and save. You can run it immediately, schedule it, or embed it as a shortcode. Snippets are sandboxed before execution — a safety check blocks known dangerous patterns. Use that feature with caution - if malformed or bad code is provided, it can break the site. Always test on non-production site first.
Yes. The Outgoing Requests Viewer logs all wp_remote_* calls site-wide.
Each record shows the requesting plugin, URL, HTTP method, response code, and
response time. This makes it easy to identify chatty plugins, unexpected
external calls, or slow API responses.
Use the Recovery Mode. Before the site breaks, generate a recovery link in Settings → Recovery Mode and deliver it to yourself via Slack, or Telegram. The link temporarily disables all the plugins, except 0-day-analytics so you can investigate what went wrong via a single-use token, allowing you to get back in.