A WordPress-aware exception debugger. It attributes frames and hooks, explains the request, suggests fixes, and keeps a local history of recent errors.
Why WP Aware Errors
WP Aware Errors replaces the generic exception screen with one that understands WordPress. Stack frames and hook callbacks are attributed to core, a plugin, a theme, an MU-plugin or Composer vendor code. It records sanitised hook arguments, names the REST route or AJAX action, checks plugin requirements, and adds WooCommerce context when WooCommerce is present. The same package loads as a normal plugin, a theme drop-in, or an MU-plugin.
A better starting point
On local and development sites, or when WP_DEBUG is on outside production, WP Aware Errors renders the failure itself. It refuses to render in production unless you explicitly allow it. Recent errors stay under Tools → WP Aware Errors.
In practice
How the product fits into the work you already do.
The capabilities behind the product.
Stack frames and hook callbacks are attributed to WordPress core, plugins, themes, MU-plugins or vendor code.
Recent hooks keep a bounded, sanitised snapshot: type, count and keys, not a deep copy of large payloads.
The screen names the REST route, method and parameters, or the AJAX action that was running.
Reads Requires Plugins, and checks WordPress and PHP requirements. WooCommerce extensions are checked against WC requires at least and WC tested up to.
When WooCommerce is present, the screen can show version, wc-ajax, HPOS, cart count and total, and the current page.
Built-in solution providers, plus a filter so a project can add its own.
A compact history of recent errors under Tools → WP Aware Errors. It can be turned off or capped.
File links open in Cursor or VS Code, and the screen can copy an AI-ready context for the error.
Plugins, themes, MU-plugins, hooks, REST and admin-ajax.
Optional context and extension compatibility headers. The package still runs without WooCommerce.
Stack frames can open as local editor links.
The same entry file detects a normal plugin, a theme drop-in under wp-content/themes, or an MU-plugin loader. There is no separate theme edition.
Classes live under src/ with a small PSR-4 autoloader. WordPress does not need Composer to run it.
The screen does not render in production unless WP_AWARE_ERRORS_ENABLED and WP_AWARE_ERRORS_ALLOW_PRODUCTION are both true.
dropins/fatal-error-handler.php can be used as wp-content/fatal-error-handler.php for failures that happen before the full package boots.
The error screen can include request paths, hook names, query text when SAVEQUERIES is on, and parts of the request. Headers and known secrets are redacted. Do not enable the production override on a public site.
Your toolkit, your choice
Choose an individual product licence or ask about Nought Suite. Contact us for pricing and availability.
Individual
Discuss this product and the right licence for your sites.
Ask about WP Aware Errors ↗The toolkit
Connected WordPress tools, with individual and agency options.
Explore the Suite ↗Remote operations
Some Nought.io plans include Suite products. What’s included depends on your plan.
Explore Nought.io ↗No. Query Monitor is a broad development panel. WP Aware Errors is the screen you get when an exception or fatal happens, with WordPress ownership, hooks and a local history of those failures.
Not by default. It renders for local and development environments, or when WP_DEBUG is on outside production. Production needs two explicit constants before it will show the screen.
Yes. Require wp-aware-errors.php from the theme and it reports Theme Drop-in mode. An MU-plugin loader is detected the same way.
No. WooCommerce version, HPOS, cart and wc-ajax context appear only when WooCommerce is installed.
Yes. Filter wp_aware_errors_solution_providers and add a class that implements the solution provider interface.
Also in the toolkit
Nought Suite The collection of WordPress products built by Nought. Buy one, or licence the lot. ↗ Files A WordPress-aware file manager and code editor for agencies and developers who need to work inside wp-content without FTP theatre. ↗ Guard Nought's security layer. Remote checks, site health and integrity signals processed off-site in Rust, with visibility in Nought.io. ↗ Restore & Reserve A WooCommerce workflow for one-off pieces. Buy unrestored, reserve with a deposit, follow the workshop, then pay the balance when the work is finished. ↗