Enable ThemeRouter Logging and Frontend Debugging

Use ThemeRouter logs and administrator-only frontend debug output to inspect routing decisions.

ThemeRouter includes separate logging and frontend debugging controls. Use them temporarily when a route selects an unexpected theme or when a cache obscures a settings change.

Enable diagnostics

  1. Open Settings > ThemeRouter as an administrator.
  2. Enable logging when you need a persistent record of routing activity.
  3. Enable frontend debugging when you need to inspect the current request decision.
  4. Save the settings and reload the affected frontend URL.
ThemeRouter Tools screen showing system status, theme preview, caching, debugging, logging, and settings import and export controls
Use Tools to enable Debugging or Logging temporarily, then disable them when the investigation is complete.

Record the useful evidence

  • Exact URL and whether the browser is logged in.
  • Expected theme and actual theme.
  • Matched resource type and saved assignments.
  • Cache layers purged before the test.
  • Debug output or relevant log entries.

Disable diagnostics after use

Frontend debug access is administrator-only by default, but diagnostic output should still be disabled when the investigation is complete. Avoid leaving verbose logging enabled on a busy production site.

Frontend debug access is administrator-only by default. Developers can further customize authorization with the themerouter_can_user_view_debug filter.

Was this helpful?