oik plugins
oik-plugins provide two plugins for problem determination.| Plugin name and description | Plugin links | Version, total downloads, last update, tested |
|---|---|---|
| oik-bwtrace debug trace for WordPress | oik-bwtrace | 3.4.0 August 19, 2022 6.0.1 |
| oik-debug-filters debug deprecated code | oik-debug-filters |
oik-debug-filters, since the functionality is now available in oik-bwtrace.
Other plugins from WordPress.org
The following plugins are available from WordPress.org. You may find these suit your needs.| Plugin name and description | Plugin links | Version, total downloads, last update, tested |
|---|---|---|
| Debug Bar Adds a debug menu to the admin bar that shows query, cache, and other helpful debugging information. | debug-bar home | 1.1.4 1,363,025 November 18, 2022 6.1.3 |
| Developer A plugin, which helps WordPress developers develop. | developer home | 1.2.6 198,572 April 14, 2016 4.5.29 |
| Log Deprecated Notices Logs the usage of deprecated files, functions, and function arguments, and identifies where the deprecated functionality is being used. | log-deprecated-notices home | 0.4.1 149,014 June 25, 2021 5.8.7 |
| Query Monitor Query Monitor is the developer tools panel for WordPress. | query-monitor home | 3.12.3 7,759,977 May 17, 2023 6.2.2 |
| debug-my-plugin | No info available | |
| debug-objects | No info available | |
| Debug This Peek under the hood with sixty debugging reports just one click away. | debug-this home | 0.6.4 135,698 March 30, 2023 6.2.2 |
Comparison of oik-bwtrace with other debug plugins
Most of the debugging plugins on WordPress.org display debug information for the current page that you’re viewing. oik-bwtrace records all the server activity in its raw form, in a separately viewable log file. It provides the capability to trace the processing flow. You can use it to see what’s happening in AJAX requests and other background requests. Think of the bw_trace2() as a super advanced var_dump() with contextual information. If you need to find out where something’s being called then you can use bw_backtrace() to obtain debug_backtrace() output in the trace file. Using the most advanced feature, Ad hoc tracing ( added in v2.0.6 ), you can specify a number of hooks and getoik-bwtrace to produce trace output for those hooks.
All without having to change any code.
