{"id":11465,"date":"2026-06-02T12:03:57","date_gmt":"2026-06-02T04:03:57","guid":{"rendered":"https:\/\/aeosub.com\/wphi-diagnostic-suite-lite\/"},"modified":"2026-06-02T12:03:57","modified_gmt":"2026-06-02T04:03:57","slug":"wphi-diagnostic-suite-lite","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/wphi-diagnostic-suite-lite\/","title":{"rendered":"WPHI Diagnostic Suite Lite"},"content":{"rendered":"
\"WPHI<\/div>\n
\n
LethaldiranMX Insight<\/div>\n
\n
\n

WPHI Diagnostic Suite Lite addresses a critical gap in WordPress maintenance by translating raw, intimidating PHP error logs into structured, actionable “error maps” that attribute issues directly to their originating plugins. By parsing error logs, determining frequency, and providing plain-English explanations alongside targeted WP-CLI commands, it demystifies debugging for both non-technical site owners and busy agency developers. Its read-only architecture ensures that diagnosing complex site failures remains a zero-risk operation, avoiding the database bloat or accidental data corruption often associated with automated repair tools. This makes it an invaluable first-line diagnostic utility during post-update triage or client onboarding.<\/p>\n

Best Fit & Operational Role:<\/strong> This plugin is an excellent fit for agency developers, freelance maintainers, and site owners who need to quickly isolate the root cause of white-screen-of-death errors or performance degradation without the overhead of heavy, continuous monitoring suites on production environments. It serves as a lightweight, on-demand diagnostic layer in the WordPress admin, bridging the gap between raw server logs and user-facing dashboards. Operationally, it streamlines the troubleshooting workflow by isolating noise, allowing teams to verify site health immediately before and after core or plugin updates without modifying any underlying database records.<\/p>\n

Potential Limitations & Pitfalls:<\/strong> While the read-only, SELECT-only database approach minimizes operational risk, the plugin’s utility depends heavily on the server’s PHP error logging configuration; if the server does not write to a standard, accessible log file, the diagnostic capabilities may be limited. Additionally, parsing massive, unrotated error logs on low-resource hosting environments could temporarily spike CPU usage during the initial scan. Aside from these environmental dependencies, no inherent security risks or structural limitations were identified based on the available information.<\/p>\n<\/div>\n<\/div><\/div>\n

\n
\n \"WPHI <\/p>\n
\n
Plugin Specification<\/div>\n

WordPress.org Official Data<\/small>\n <\/div>\n<\/p><\/div>\n\n\n\n\n\n\n\n
Developer<\/th>\nbsha100<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv3.1.1<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n6.0 \/ 6.9.4<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-06-02 4:00am GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details -><\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
Find out exactly why your WordPress site is slow, broken, or throwing errors \u2014 see which plugin caused it, which update triggered it, and get specific …<\/div>\n

You already know something is wrong. This plugin tells you what, why, which plugin is responsible \u2014 and exactly how to fix it.<\/strong><\/p>\n

\ud83d\udd34 Try the live demo \u2014 no install required<\/a><\/strong><\/p>\n

Most WordPress diagnostic tools show you a list of problems. WPHI Diagnostic Suite goes further: it reads your PHP error log, groups every error by severity and frequency, traces each one back to the plugin that caused it, and checks whether a recent update triggered it. It then gives you a structured “error map” for each error \u2014 plain-English explanation, probable cause extracted from the actual function or class that failed, impact level, numbered fix steps, and WP-CLI commands specific to the error type.<\/p>\n

It also includes a live error log with its own PHP error handler. Clear it, reproduce the problem, and see exactly which new errors appeared \u2014 without wading through weeks of historical noise. This makes it a practical debugging workflow, not just a report.<\/p>\n

It does all of this without touching a single row of your data. Every query is SELECT<\/code>-only. No cleanups, no automation, no risk.<\/p>\n

Who is this for?<\/h4>\n

\u2705 Site owners<\/strong> who see “something is wrong” on their dashboard and don’t know where to start.<\/p>\n

\u2705 Developers<\/strong> who need to diagnose a client site quickly without installing Query Monitor on production.<\/p>\n

\u2705 Agencies<\/strong> managing multiple WordPress sites who need a fast, reliable read on site health before and after maintenance.<\/p>\n

\u2705 Anyone<\/strong> who has ever looked at a PHP error log and not known what to do next.<\/p>\n

What makes this different<\/h4>\n

Most diagnostic plugins show you numbers. This one tells you what the numbers mean for your<\/em> site, right now \u2014 and which plugin is responsible.<\/p>\n

Error maps, not error lists.<\/strong> When the Error Log Viewer finds a PHP fatal error, it doesn’t just show you the message and file. It opens a structured “error map” with five sections: what this error class means in plain English, the probable cause based on the actual function or class name extracted from the message, the impact on visitors, numbered fix steps specific to this error type, copyable WP-CLI commands, and a prevention tip. A “Call to undefined function wc_get_cart()” gets different advice than a “Cannot redeclare foo()” \u2014 because they’re different problems.<\/p>\n

A live error log you can clear and retest.<\/strong> Beyond your main PHP error log, the plugin registers its own PHP error handler that captures errors into a separate log you control. Clear it, reproduce the issue, and see exactly which new errors appear \u2014 without wading through weeks of accumulated historical noise. This turns error diagnosis into an actual workflow rather than a guessing game.<\/p>\n

Change correlation \u2014 which update caused it.<\/strong> The What Changed? module tracks every plugin update, activation, and WordPress core update as a timestamped event. When a PHP error appears, it calculates a 0\u201399 correlation score between the error and the most likely change that caused it \u2014 using file-path matching (the error originates inside the updated plugin’s folder) as the primary signal, scoring 80\u201399 when it’s near-certain. You can see at a glance whether last night’s WooCommerce update is responsible for today’s fatal errors.<\/p>\n

Plugin attribution everywhere.<\/strong> It’s not enough to know you have 12 custom database tables. You need to know which plugin owns each one<\/em>, how many rows each table has, and what would happen if you deactivated that plugin. The Blast Radius module traces every custom table, every scheduled cron job, and every REST API namespace back to the plugin that created it \u2014 using callback Reflection, file scanning, and a curated fingerprint database covering 30+ popular plugins.<\/p>\n

Recommended diagnostic paths based on your live data.<\/strong> The dashboard reads your current error log, autoload size, overdue cron count, and pending update count, then surfaces the two or three diagnostic paths most likely to lead you to the root cause of your current problem \u2014 in the right order. No generic checklists. Paths are ordered by how strongly your live data points to each scenario.<\/p>\n

The Modules<\/h4>\n

\ud83c\udfe5 Health Score Dashboard<\/strong>
\nAn animated 0\u2013100 gauge computed from all module findings. Issues are listed with severity labels and direct links to the relevant module. Opens instantly \u2014 no page scan required.<\/p>\n

\ud83d\udd0d Error Log Viewer<\/strong>
\nParses your PHP error log and groups identical errors by severity and frequency. Each group shows severity, occurrence count, first and last seen timestamps, file path, line number, and a full error map with fix steps and WP-CLI commands. A “What Changed?” button on each card checks whether a recent update correlates with the error’s appearance. Error log search filters live without a page reload and composes correctly with pagination.<\/p>\n

Also includes a live error log<\/strong> powered by the plugin’s own PHP error handler \u2014 separate from debug.log<\/code>. Clear it at any time, reproduce the issue, and see exactly which new errors are generated. This makes it a practical debugging workflow: clear, reproduce, read, fix, repeat.<\/p>\n

\ud83d\udce1 What Changed? \u2014 Timeline Correlation<\/strong>
\n“Something broke after an update” is the most common WordPress problem \u2014 and the hardest to diagnose without this. Tracks plugin updates, activations\/deactivations, WordPress core updates, and theme changes as timestamped events. Displays them on an interactive SVG timeline alongside PHP error spikes. Each error-to-change pairing gets a 0\u201399 confidence score: file-path matching (the error originates inside the updated plugin’s folder) scores 80\u201399 \u2014 near-certain attribution. Clicking any correlation finding shows the confidence score, the reasoning, and the specific files involved.<\/p>\n

\ud83d\uddc4\ufe0f DB Health Inspector<\/strong>
\nShows every autoloaded option ranked by size with colour-coded severity. Flags orphaned postmeta rows left by removed plugins, and lists every table exceeding 50 MB. Identifies the exact options driving your autoload overhead.<\/p>\n

\u26a1 Autoload Governor<\/strong>
\nFull per-plugin autoload attribution \u2014 know which plugin owns each option. Includes Deep Autoload Diagnostics with five detection passes: orphaned options from removed plugins (80+ plugin fingerprint database), autoloaded transients, duplicate cache clusters, migration remnants from backup tools, and stale WooCommerce sessions. Each finding shows the size in KB and includes a ready-to-run WP-CLI command.<\/p>\n

\ud83c\udfaf Blast Radius Analyzer<\/strong>
\nEvery custom database table attributed to its owning plugin \u2014 with name, version, and approximate row count. Every non-core cron job attributed via callback Reflection and hook-name fingerprinting. Know exactly which plugins have the deepest footprint on your site and what removing them would affect.<\/p>\n

\ud83d\uddbc\ufe0f Asset Inspector<\/strong>
\nEvery JavaScript and CSS file WordPress enqueues on the front end, with individual file sizes and running totals. If a plugin loads a 400 KB script on pages where it’s not needed, this is where you find it.<\/p>\n

\ud83d\udd50 Cron Inspector<\/strong>
\nEvery WP-Cron and Action Scheduler job with its next run time and recurrence interval. Overdue jobs are highlighted \u2014 they run on the next page request and spike load for that visitor.<\/p>\n

\ud83d\udca3 Time Bomb Detector<\/strong>
\nChecks your SSL certificate expiry and warns you 30 days in advance. An expired SSL certificate is a site outage your visitors experience before you do.<\/p>\n

\ud83d\udda5\ufe0f Server & PHP Environment<\/strong>
\nPHP memory limit, max execution time, upload limits, OPcache status, and server software details. The configuration ceiling that caps everything else your site can do.<\/p>\n

\ud83d\udcc4 Export Report<\/strong>
\nDownloads a self-contained HTML report covering health score, database metrics, error log summary, and system snapshot \u2014 useful for sharing findings with a developer or keeping as a pre-maintenance baseline.<\/p>\n

Recommended Diagnostic Paths<\/h4>\n

The dashboard evaluates seven common WordPress problem scenarios against your live site data and surfaces the ones most relevant right now:<\/p>\n