PressCare Error Doctor

Written by Kevin Kemp. These are the plugin screens published at presscare.com/presscare-error-doctor. The interface is HTML, CSS, and JavaScript in wp-admin. The scan behind it is PHP. The readme is on GitHub.

View the code Product page

The workflow

Four steps sit at the top: a private local scan, the action plan, an optional AI explanation, and repair help. The date range decides which log lines enter the plan. Export and print stay on the sanitized report.

Error Doctor workflow, date range set to the last 7 days, and a scan result of 25 events grouped into 1 finding. — The scan controls and the first result. Nothing in this step leaves the site.

What the scan found

Repeated lines become one finding, filed under the plugin, theme, or WordPress area that owns the path. Critical errors are called out on their own. The rest stay collapsed until someone opens them.

Error Doctor action plan with 25 events in one WooCommerce Payments finding and no active critical errors. — Twenty-five events, one area, one grouped finding.

An expanded WooCommerce Payments warning with resolution steps, Ask PressCare AI, repair help, and a consent box for sending sanitized evidence. — The opened finding, and the consent step before any provider is asked.

Repair help and the site snapshot

The steps for a finding are on the screen. A PressCare repair request is a separate choice. The site snapshot is read-only context: WordPress, PHP, the database, transients, and autoloaded options. Opening it does not change those options.

Error Doctor comparing included do-it-yourself guidance with optional PressCare repair help. — Do-it-yourself guidance beside the optional repair request.

Read-only site snapshot with WordPress 7.0.2, PHP 8.2.33, transient counts, and autoloaded option sizes. — Environment, transients, and autoloaded options. Values of those options are not in the report.