The oik-bwtrace plugin provides a trace mechanism for problem determination of WordPress plugins and themes and even core code.

• The primary purpose of debug trace is to help in the development of PHP code: plugins or themes.
• The primary purpose of action and filter trace is to help you follow the sequence of events in the server.
• This plugin provides the admin interface to trace functions and action and filter tracing built into plugins that use the oik / bw APIs.

• Trace APIs
• An introduction to problem determination with oik-bwtrace – debug trace for WordPress
• Getting started with oik-bwtrace v3.0.0
• Viewing trace files
  • Viewing REST request trace files
• Settings > oik trace options
  • Trace files
  • Trace options – requests sections
  • Trace options – trace records
  • Daily trace summary
  • Trace Information box
• Settings > oik action options
  • Action options – options
    • Count action hooks and filters
    • Trace deprecated messages
    • Trace Error, Warning and Notice messages
    • Trace ‘wp’ action
    • Trace ‘wp’ global wp_rewrite
    • Purge trace file if no errors
    • Trace ‘shutdown’ included files
    • Trace ‘shutdown’ saved queries
    • Trace ‘shutdown’ output buffer
    • Trace ‘shutdown’ trace functions count
    • Trace ‘shutdown’ status report
  • Settings > oik action options – Ad hoc tracing
    • Other hooks to trace
    • Filter results to trace
    • Trace the global post object
    • Trace attached hook functions
    • Hooks to debug backtrace
    • String watch for this string
• Start tracing from wp-config.php
• Trace output file
• WordPress plugins for debugging or problem determination
• oik-bwtrace Must-Use and Drop-In logic
• Deprecated or deleted or legacy logic and documentation
  • oik-bwtrace – requirements for a standalone plugin
  • Debug trace dependency on the oik base plugin
  • oik-bwtrace modifications to wp-includes/plugin.php
  • oik-bwtrace action and filter trace file – bwaction.loh – Deprecated