Web Guy

<a href="https://github.com/webguyio/support" rel="nofollow ugc">💬 Ask Question</a> | <a href="mailto:webguywork@gmail.com" rel="nofollow ugc">📧 Email Me</a>
The fastest and easiest way to switch debug mode on/off and view PHP info directly from the admin.
<ul>
<li>Normally, to enable debug mode, you’d have to manually add the following to wp-config.php: <code><?php define( 'WP_DEBUG', true ); ?></code></li>
<li>Normally, to view the server’s PHP version and other info, you’d have to manually upload a file with: <code><?php phpinfo(); ?></code></li>
</ul>
With Debug Switch, this is handled automatically.
How?
Simply activate the plugin to enable and deactivate the plugin to disable them when you’re done debugging.
Why?
There are a dozen other debugging plugins that already do this (more or less), so why create another?
Well, I already tried them all, and they just felt clunky and unnecessarily overcomplicated. I got tired of having to manually switch debug mode on and off and these other plugins didn’t offer a simple way to do that without also adding a bunch of other bells and whistles that I found to just be in the way, so I made something simpler.

Debug Switch

The fastest and easiest way to switch debug mode on/off and view PHP info directly from the admin.

AVATTAVA

Debug Activation Errors 2.0 shows you the issues during plugins activation on WordPress plugins page: plugins.php
A developers’ plugin that allows to debug the ambiguous error message: “The plugin generated ### characters of unexpected output during activation”.
If you notice messages like “headers already sent”, problems with syndication feeds or other issues, activate Debug Activation Errors 2.0 and deactivate any suspicious plugin.
Then, activate the possible culprit again and you will see if there are any issues during its activation. You can repeat this operation as many times as you want…
Whenever you have solved the issues and to stop seeing any messages, you can deactivate our plugin, Debug Activation Errors 2.0
This plugin is not designed to operate on a Multisite install (Network Mode) and we do not guarantee any results in those conditions.
@@@@@ READ CAREFULLY @@@@@
Alongside with the use of Debug Activation Errors 2.0, you should update the file wp-config.php with the below snippet of code:
/** 
 * For developers: WordPress debugging mode. 
 * 
 * Find the line of code >> define( ‘WP_DEBUG’, false ); << and replace it with the 3 lines of code below. 
 * You must set WP_DEBUG to “true” to enable the display of notices during development. 
 * WP_DEBUG_DISPLAY should always be “false”, unless you have a very strong reason to change its value to “true”. 
 * You should have a debug.log file in WordPress, if not, you must create it and set WP_DEBUG_LOG to “true”. 
 * It is strongly recommended that plugin and theme developers use WP_DEBUG in their development environments, with caution. 
 */ 
define( ‘WP_DEBUG’, true ); 
define( ‘WP_DEBUG_DISPLAY’, false ); 
define( ‘WP_DEBUG_LOG’, true );
<h3>Support</h3>
Please, use the WordPress.org forums for community support at https://wordpress.org/support/plugin/debug-activation-errors and if you spot a bug or if you have a suggestion to improve the code functionality, you can contact us at contact@avattava.xyz

Debug Activation Errors 2.0

Debugs errors and shows you the issues during WP plugins activation.

Debug Switch vs Debug Activation Errors 2.0