Marin Atanasov

Automatically propagates the wpMandrill settings from the main site to all subsites, still allowing each subsite to manually override them.
<h3>Getting Started</h3>
Go to Settings -> Mandrill and setup at minimum your API key, FROM name and FROM email. This will have your Mandrill plugin enabled and connected. This is all that is necessary for the wpMandrill Multisite plugin to work. These settings will now be automatically be propagated to the subsites that have no Mandrill settings. You can then manually override them for each site, if you prefer.
<h3>Further customization for developers</h3>
The plugin offers several hooks that allow developers to modify the default plugin behavior.
<h4>wpmandrill_multisite_site_id</h4>
$site_id (int). The ID of the current site.
This filter allows you to modify the ID of the current site. Unless the network is a multi-network (a network of multisite networks), this will usually be <code>1</code>.
<h4>wpmandrill_multisite_propagation</h4>
$propagate (bool). Whether the settings should be propagated.
$blog_id (int). The ID of the currently iterated blog. Allows custom logic to be built.
This filter allows you to specify whether the wpMandrill settings should be propagated to the subsites. Using the <code>$blog_id</code> you can build a custom logic to disable propagation only for a certain blog. Or if you ignore <code>$blog_id</code>, you can globally disable the propagation.
<h4>wpmandrill_multisite_settings</h4>
$mandrill_settings (array). An array of all wpMandrill settings that will be propagated.
$blog_id (int). The ID of the currently iterated blog. Allows custom logic to be built.
This filter allows you to modify the wpMandrill settings that will be propagated to the subsites. Using <code>$blog_id</code>, you can use custom logic to change the settings only for a certain blog.
<h3>Ideas and bug reports</h3>
Any ideas for new modules or any other additional functionality that users would benefit from are welcome.
If you have an idea for a new feature, or you want to report a bug, feel free to do it here in the Support tab, or you can do it at the Github repository of the project:
https://github.com/tyxla/wpMandrill-multisite/

wpMandrill Multisite

Automatically propagates the wpMandrill settings from the main site to all subsites, still allowing each subsite to manually override them.

RexAK

Install wpMandrill first! 🙂 I use this in my personal localhost development flow, to allow emails to be sent out from a local install. Thought I\’d share it with you and make it an easy install for developers.
If you use this, let me know!!!
Basically, make sure the wpMandrill plug is installed, setup, and running on your local install, however, the plugin will do nothing if wpMandrill is not installed. 😉
Add this plug-in, go find it in the SETTINGS section of your WP install and config it.
This plug in will not reroute other plugs, like Mailpoet, that use their own mail handling or SMTP intercepts.
It works great for things like normal WordPress emails (password reminders, new users, etc,) Woocommerce, or anything that uses wp_mail to send.

WP Reroute Mandrill

I've used an alternate plugin for rerouting mail forever but it always lets me down when it comes to Mandrill. As is always the case in the Wordpress world: Ask and ye sha'll receive!
Hooray! Now I can test my Mandrill-enhanced applications without fear of unintended mail going out to users. 
Awesome! A+++



EXACTLY WHAT I NEEDED!

Reroutes All Mail going through the wpMandrill Plugin to email address(s) of your choice.

wpMandrill Multisite vs WP Reroute Mandrill