Subscribe

WP-Debug

WebDevStudio has created WP-Devel which uses the foundation of WP-Debug and has added enhancements. I’m no longer updating WP-Debug but instead pointing to their work.

I was using my StumbleUpon, and I came across Krumo which is a PHP debugging application. It allows you to see the content of server variables, cookies, and a lot more including specified variables such as $wp_query! After a short while I had a running WordPress plugin which should be an asset for WordPress developers.

That’s it! As long as you’re logged in you’ll see the expandable menus in the footer of your page (nothing is shown to your visitors). It does rely on having the wp_footer() call in your theme so ensure that’s there if you don’t see anything.

Configuration

Krumo comes with some default styles: default, blue, green, orange, and scablon.com. It is set to default which works the best with the default WordPress theme. If you would like to change it you can go to the “krumo” folder of the plugin and edit the “selected” value in the krumo.ini file (you might have to adjust the styles depending on how CSS inheritance from your theme throws things off).

[skin]
selected = "default"

I have most of the Krumo API in the plugin, but you can add/remove at your lesiure. If you want to check a variable then simply add to lines 14, but you can see on line 14 that I had to declare WordPress variables as global, because the content is outside the loop. Simply add a global variable to line 12 if needed.

Related

21 Comments

Hi There Chris –
This looks at a great plug-in… thank you very much. I recently ran into some slow-loading page issues for my WordPress websites and tried a bunch of things to address the issue(s) (see forum post at http://wordpress.org/support/topic/141011).

I plan to blog about your plugin at OpenSourceWebMaster.com. Do you have a donation button for your plugin?
– Scott

thanks for the great plugin. I was always looking for such structured information for debugging purposes.

I did some modifications to the plugin code and also to the krumo class itself. If you are interested in this code, I would be happy to share this.

I did the following changes:
– Krumo output is now also displayed on the admin pages of WordPress
– A developer can call the debug functions itself. In this case it is assumed that she would like only to see the requested information. The predefined bunch of krumo calls are skipped in this case
– If a developer calls the debug function itself, the output will also go to the footer of the page
– Krumos recursion detection wasn’t acutally a recursion detection but a reference detection. This lead to more recursion warnings as necessary

Hi, I accidentally installed this on my PHP4 hosting service and found nothing in my WP install worked. All failing looking for the debug_print_backtrace() function. In your btev.php module you call this twice, but you only check for it’s existence in the first one. Fixing it was a simple matter of copying the code block from the first call (lines 1054-1065) over the second call (from line 1108).