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.

06
Source LifecycleLocal Versions

How to tell whether an error continued after a plugin, theme or WordPress version changed

Titanium does not call a remote version service. It records locally installed source versions when matching errors are observed and compares retained observations with the currently installed source.

Read source lifecycle evidence

  1. Find the grouped error and read its source label. Titanium can identify plugins, MU-plugins, themes, WordPress Core, custom wp-content code or an unknown source.
  2. Look for First observed on v… to see the earliest retained source version associated with that group.
  3. Read the latest lifecycle label to see the version where the most recent matching error was observed.
  4. If the source changed versions and the error continued, treat that as evidence that the update did not stop the same grouped failure.
  5. If the installed source version is newer than the last-error version, the UI can show that no recurrence has yet been seen on the current version.
  6. Keep watching the group until enough time has passed to decide whether the update really resolved the pattern.

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