scribu

When running WordPress MultiSite, you have a very handy feature called network activation. It allows you to activate a plugin for the entire network of sites. The trouble is that it only does half the job.
Some plugins have an install procedure that is meant to be run only on activation. However, when you do a network activation, that install procedure is only run for the current site. So, you end up with plugins not working properly on all the other sites.
What this plugin does:
<ul>
<li>when doing a network de/activation, it triggers the de/activation hook on all sites in the network</li>
<li>when creating a new site, it triggers the activation hook for all active network plugins on that site</li>
</ul>
Links: <a href="http://scribu.net/wordpress/proper-network-activation" rel="nofollow ugc">Plugin News</a> | <a href="http://scribu.net" rel="nofollow ugc">Author’s Site</a>
<h4>Development</h4>
<ul>
<li>Contribute Code at <a href="https://github.com/scribu/wp-proper-network-activation" rel="nofollow ugc">https://github.com/scribu/wp-proper-network-activation</a></li>
<li>Contribute Translations at <a href="https://translate.foe-services.de/projects/proper-network-activation" rel="nofollow ugc">https://translate.foe-services.de/projects/proper-network-activation</a></li>
</ul>

Proper Network Activation

Avoid errors when using WordPress MultiSite network activation

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.

Proper Network Activation vs Debug Activation Errors 2.0