{"id":296,"date":"2012-10-03T14:21:13","date_gmt":"2012-10-03T14:21:13","guid":{"rendered":"http:\/\/oik-plugins.co.uk\/?post_type=oik-plugins&p=296"},"modified":"2024-09-21T11:23:14","modified_gmt":"2024-09-21T11:23:14","slug":"oik-bwtrace-debug-trace-for-wordpress","status":"publish","type":"oik-plugins","link":"https:\/\/www.oik-plugins.com\/oik-plugins\/oik-bwtrace-debug-trace-for-wordpress\/","title":{"rendered":"oik-bwtrace – debug trace for WordPress<\/span>"},"content":{"rendered":"\n

Dynamically activated debug trace for WordPress, with Ad hoc<\/em> action and filter hook tracing.

The oik-bwtrace plugin for WordPress enables you to see what’s going on in your server. It provides a user interface to dynamically activate tracing logic for browser requests, AJAX requests, REST API requests and command line interfaces. <\/p>\n\n\n\n

Use oik-bwtrace to see what’s actually happening in your WordPress server.<\/p>\n\n\n

<\/span><\/div>\n\n\n\n\n\n\n

Most of the documentation has been updated for oik-bwtrace v3.0.0. If you find a problem please raise an issue at \r\n\t\t\r\n\t<\/SVG> bobbingwide\/oik-bwtrace<\/a><\/p>\n\n\n\n

Depending on the level of trace you choose the trace output may include some standard trace records produced by oik-bwtrace and trace records from the dormant debug trace function calls implemented in plugins and themes.<\/p>\n\n\n\n

For simple problem determination of your own code, if PHP debugging is not an option, you can use the bw_trace2<\/a>() and bw_backtrace<\/a>() calls.<\/p>\n\n\n\n

If you want to follow WordPress’s execution you may also want to activate the action trace logic. Using the action trace helps you to determine the sequence of action and filter calls in your WordPress site without having to resort to using a PHP debugger or other low level profiling functionality.<\/p>\n\n\n\n

Debug trace for WordPress<\/h3>\n\n\n\n