Skip to content
Admin Plugins
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.

10
MultisiteRetention & Privacy

How to use Titanium Error Intelligence on Multisite and understand what stays local

WordPress debug logging is installation-wide on Multisite, so Titanium uses network-scoped settings and one scanner. The same local-first design applies to grouped error history, request-impact evidence and the optional health summary.

Set up Multisite correctly

  1. Install the plugin from Network Admin and network activate Titanium Error Intelligence.
  2. Use the plugin admin UI from the main site's wp-admin as intended by the network-aware workflow.
  3. Remember that intelligence data and settings are network-scoped because the debug log is shared across the installation.
  4. Allow request context to be captured across sites while one five-minute scanner runs from the main site to avoid duplicate processing.
  5. Review grouped intelligence within its seven-day retention window and download raw logs separately if you need a longer archive.
  6. If another installed Titanium component needs compact local health data, it can call titanium_error_intelligence_get_health_summary().

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