Titanium Error Intelligence Tutorials

10 practical ways to turn WordPress PHP errors into clearer local diagnostics.

These step-by-step tutorials cover first-time setup, the Monitoring Self-Test, grouped error behavior, Request Impact, source-version lifecycle, the log viewer, live wp-admin alerts, private log storage, file tools, Multisite and the plugin's seven-day local retention model.

Get Free Version Plugin Overview

Grouped critical errors
Request Impact Map
Monitoring Self-Test
Local by default

Step-by-step PHP error monitoring tutorials.

Start by making sure WordPress can write a debug log, then verify the pipeline before relying on the intelligence cards. Use the behavior and impact evidence to narrow a problem, and only then move into the raw log or file tools when deeper inspection is needed.

Log ViewerRaw Evidence

How to search, filter and auto-refresh the configured WordPress log

The browser viewer complements grouped intelligence. Large files are read as a bounded tail so wp-admin stays usable, while the complete allowed file remains available for download when you need every line.

Inspect the raw log efficiently

Open the configured log in Titanium Error Intelligence.
Choose how many recent lines you want loaded, then use Search loaded lines to find a message, file or path fragment.
Use the All, Error, Fatal, Exception, Cron, Warning, Notice, Deprecated or Database filters to narrow what is shown in the browser.
Enable Auto-refresh when you are reproducing a problem. The viewer checks for updates every 10 seconds while active.
If the configured log has not been created yet, leave auto-refresh enabled while reproducing the issue; the viewer can load the file once WordPress creates it.
Download the complete log when the viewer indicates that only the newest bounded part is being displayed.

Viewer and editor limits

Search and filters operate on the lines currently loaded in the browser, not an unlimited server-wide index.
The viewer intentionally bounds large files to keep the admin page lightweight.
The built-in editor is intended for smaller supported files and is limited to files up to 5 MB.
Saving the editor replaces the complete file content, so use it carefully.
For a full forensic archive, download the file before clearing or editing it.

Debugging tip: Filter first, search second. For example, choose Cron and then search a hook or plugin name to remove unrelated warnings from the browser view.

Start with logging, then verify the pipeline before interpreting the dashboard.

The most reliable order is simple: enable or confirm the debug log, run the self-test, wait for real matching errors, inspect behavior and impact, then use the raw log only when you need deeper evidence.

Get Free Version

Need the complete feature overview?

Read the Titanium Error Intelligence plugin page for grouped error behavior, Request Impact, source lifecycle, Monitoring Self-Test, live wp-admin alerts, private log storage and the authenticated log tools in one place.

View Plugin Overview