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

paulmac

WordPress allows posting via email, but must be told to check for emails. This is achieved by calling wp-mail.php using either a cron job, or by including a hidden iframe in your blog footer.
This plugin adds the iframe to the blog footer without editing the theme – updating your theme won’t break your ability to email in posts to WordPress.

Email Post Activation

Adds an iFrame to your blog footer to automatically activate any posts written by email.

Proper Network Activation vs Email Post Activation