wpsnoop: fix WP-Debug plugin conflicts, errors & issues
When the plugin WP-Debug conflicts or throws a PHP error we hope wpsnoop can help you to fix the issue quickly.
Discover which shortcodes wp-options PHP functions database tables and files are created by WP-Debug, plus learn which plugins and/or themes could be in conflict with WP-Debug.
Troubleshooting theme and plugin conflicts is easier when you know what WP-Debug leaves behind after uninstalling it from a WordPress installation, there is a list down below for your convenience.
Expert advice is recommended if you are not technically proficient with PHP, MySQL etc. View support options for WP-Debug
When you need professional help with WordPress: get help here
What does WP-Debug version 1.0 add to WordPress? Answers Here.
This is an automatically generated report - it is possible for WP-Debug to perform differently in your installation, previous versions before 1.0 may have created a different set of shortcodes, used different function names or could have created entirely different database tables to store settings and operate. This is not an exhaustive list but shows how version 1.0 of WP-Debug behaves when installed and removed on a clean installation of WordPress.
We have not tested individual shortcodes, features or settings of this plugin but instead have concentrated on the potential for obvious errors and conflicts which can occur, if you need help with the plugin in your local installation you can get WordPress help and support for WP-Debug by clicking here.
Our testing covered the free version of this plugin there may or may not be a paid version or premium version available for purchase that unlocks additional features and could behave in a slightly or very different manner.
Summary of WordPress plugin analysis: WP-Debug
Which new files does WP-Debug add to WordPress?
This section will populate with a table showing an icon, size and filepath.
| Type & Path | Size | Conflicts |
|---|---|---|
| wp-content/plugins/wp-debug/ | 73.52kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo.css | 314.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/ | 43.53kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/class.krumo.php | 24.96kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/krumo.ini | 445.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/krumo.js | 2.14kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/ | 15.99kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/blue/ | 3.09kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/blue/bg.gif | 141.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/blue/skin.css | 2.95kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/default/ | 3.10kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/default/bg.gif | 141.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/default/skin.css | 2.96kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/green/ | 3.09kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/green/bg.gif | 141.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/green/skin.css | 2.96kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/orange/ | 3.10kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/orange/bg.gif | 141.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/orange/skin.css | 2.96kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/schablon.com/ | 3.61kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/schablon.com/collapsed.gif | 102.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/schablon.com/dotted.gif | 91.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/schablon.com/empty.gif | 101.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/schablon.com/expanded.gif | 99.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/krumo/skins/schablon.com/skin.css | 3.23kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/readme.txt | 2.04kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/screenshot-1.png | 25.97kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/wp-debug/wp-debug.php | 1.68kB | No known conflicts with other themes or plugins. |
Which new shortcodes does WP-Debug add to WordPress?
What new PHP functions does WP-Debug declare when it is active?
| Function | Conflicts | Common Errors | |
|---|---|---|---|
| krumo_styles | 1 conflict | Fatal error: Cannot redeclare krumo_styles() | |
| publish_krumo | 0 conflicts | Fatal error: Cannot redeclare publish_krumo() |
Using WP-Debug from the command line with WP-CLI
The following commands are provided for convenience and should only be used if you understand how WP-CLI works. These commands refer to a single WordPress instance and may need to be modified if you are working with a Multisite installation.
How to install WP-Debug from the command line with WP-CLI
Navigate to the root of your WordPress installation and type the following command:
How to activate WP-Debug from the command line with WP-CLI
To immediately activate WP-Debug after WP-CLI downloads the latest version you can use the following command:
How to reinstall WP-Debug from the command line with WP-CLI
To force a reinstallation of WP-Debug which overwrites the current plugin without asking for confirmation you can use the following command:
How to update WP-Debug to the latest version from the command line with WP-CLI
How to delete WP-Debug from the command line with WP-CLI
Where can you download earlier versions of WP-Debug?
Whenever possible you should use the latest version of plugins and themes, however if you have recently updated and discovered that you need to install an earlier version you may be able to download other versions of WP-Debug from the WordPress repository by visiting this link.
Please note that installing earlier versions of a theme or plugin is not generally a recommended course of action for most users and could re-introduce security, stability or other issues in WP-Debug
About our testing enviroment
Tests were conducted using Apache 2.4.29, PHP 7.2 on Ubuntu 18.04, MySQL 5.7.33 and WordPress 5.9
It is very possible that different versions of PHP such as PHP 8.0, PHP 7.4, or PHP 7.3 could behave differently with WP-Debug. Different versions of WordPress could implement the features of this plugin in slightly different ways as well.