The WP Debug Toolkit (WPDT) error log viewer provides a filter panel and a search box for narrowing down log entries. Filters and search work together — filters restrict the data set, and search narrows within the filtered results.
Press F to open the filter panel. Press F again to close it. The panel contains five filter groups:
Filter by error severity. Options:
Select one or more levels. Only entries matching the selected levels are shown.
Restrict entries to a recent time window. Options:
Select a time range to hide older entries. This is useful after deploying a change — set the time filter to 5m or 15m to see only errors that appeared since the deploy.
Filter by where the error originates in the WordPress file structure:
A dropdown listing every plugin detected in the current log entries. Select a specific plugin to show only errors originating from that plugin’s directory. The dropdown is populated dynamically based on file paths in the log data.
A dropdown listing detected themes, populated the same way as the Plugin filter. Select a theme to isolate its errors.
All active filters use AND logic. If you select Level: Warning and Source: Plugins, the viewer shows only warnings that originate from plugins. Adding a Plugin filter further narrows the results to warnings from that specific plugin.
Press 0 while the filter panel is open to reset all filters to their defaults (no filters active). All entries become visible again.
Press / to focus the search box. Type any text to search across message text and error level. Results update as you type.
Press Esc to clear the search and return to the full (filtered) view.
The search box supports inclusion and exclusion operators for more precise queries:
| Operator | Meaning | Example |
|---|---|---|
+term | Must include | +woocommerce |
-term | Must exclude | -deprecated |
Combine operators with commas to build multi-criteria searches:
+woocommerce, -deprecatedThis finds entries containing “woocommerce” while excluding any that contain “deprecated.” Use this to focus on actionable WooCommerce errors without the noise of deprecation notices.
| Search | What it finds |
|---|---|
fatal | Entries containing “fatal” anywhere |
+elementor, +database | Entries containing either “elementor” or “database” (OR logic) |
+timeout, -cron | Timeout errors not related to cron |
class-wc-order | Entries mentioning the WooCommerce order class file |
Filters and search stack. If you set Level: Error, Source: Plugins, and search for +stripe, the viewer shows only Error-level entries from plugins that mention “stripe.” This combination is the fastest way to isolate a specific problem.
