CU Debug Tool by CodeUnion

For security reasons, this plugin requires an explicit constant to be defined. Please ensure you have added define( 'CU_DEBUG', true ); to your wp-config.php file. Also, ensure you are logged in as an Administrator. Finally, keep in mind that this is a frontend-only tool — you will not see any options in the backend Admin menu.

SQL recording requires WordPress to save query history, which uses memory. By default, this is OFF. When you click "Start Recording" in the SQL tab, the plugin sets a temporary cookie that enables this feature only for your session.

Yes! Go to the "Registry" tab. The plugin uses PHP Reflection to attempt to locate the exact file and line number where the shortcode callback function is defined.

If you want to see the logs, make sure you have the following options enabled in your wp-config.php file:

1. define('WP_DEBUG', true);
2. define('WP_DEBUG_LOG', true);
3. define('WP_DEBUG_DISPLAY', false); Ensure that your debug.log file is in the default location (wp-content/debug.log).

The Dumps tab is empty by default because it only displays data that you explicitly capture. To see data here, you must use the helper function cu_dump($variable) within your theme or plugin code. It works similarly to var_dump(), but instead of breaking your layout, it safely displays the formatted data inside the debug panel. Example usage: \$my_data = ['id' => 123, 'status' => 'active']; cu_dump( \$my_data );