Yann at WP&amp;Co

This plugin has been thoroughly tested and is fully compatible with WordPress 3.0x multisite or with WPMU 2.9.
This plugin was originally named YD WPMU Sitewide Options. The name has been changed with version 3.0 to match WordPress 3.0 vocabulary and concepts. Backwards compatibility with WordPress MU has been maintained.
<h4>Centralized management of your network-wide installed plugins!</h4>
This WordPress 3.0 multisite or WPMU plugin installs a new settings page where you can choose which blog or plugin settings you want to replicate site-wide or network-wide to all your children sites. 
Any change (update) to those settings (options) on the mother site admin pages can be automatically copied to all the sub-sites (blogs).
You can choose which settings to replicate, you can decide if changes of the settings on the main blog should be automatically replicated to all blogs.
You can replicate your settings as a “one-shot” process (for example when setting up new blogs or installing a new network-wide or site-wide plugin), 
or have the plugin maintain your settings in sync on all your blogs over time.
You can decide if chosen settings will be automatically “spread” to newly created blogs or not.
You can choose to manually spread the settings only when you decide to, and not to overwrite existing individual blog settings. 
This way, you can maintain specific settings on some blogs while keeping the ability to spread default settings to new blogs.
Since version 4.0.0, the plugin can now create and copy custom database tables used by some plugins, further widening the scope of plugins that can be made network-wide manageable.
Those techniques can be used to convert any standard WordPress plugin from standalone to a versatile multisite network-wide or sitewide WPMU plugin!
You can use your main blog as a template-blog for the creation of new sites in your network: the new sites can automatically adopt any or all settings of your main blog, 
activated plugins can also be copied, as well as the settings of each plugin. This is an alternative to other commercial or non-commercial new blog defaults / new blog template plugins for WPMU.
Many other creative uses are possible.
It efficiently makes for a centralized deployment of any plugin parameter on all your WPMU blogs: the main blog acts as a “master” when setting the site-wide option, while your child blogs replicate any change in the option over time like “slaves” (a rather typical master-slave replication pattern).
The plugin has its own admin options page (settings page).
It is fully internationalized.
Base package includes .pot file for translation of the interface, and English, French, Dutch and German versions.
<h4>Compatibility</h4>
This plugin has been successfully tested to convert the following standalone WordPress plugins to network-wide Worpress 3.0x multisite or sitewide WordPress MU plugins with centralized administration:
<ul>
<li>All WordPress core-options including WordPress 3.0x default theme header options, active plugins, administrator e-mail, commenting otpions and search engine accessibility (public/private status), etc.</li>
<li><a href="http://WordPress.org/extend/plugins/akismet/" rel="ugc">Akismet plugin</a> credentials (API Key)</li>
<li><a href="http://WordPress.org/extend/plugins/yd-spread-parameter/" rel="ugc">YD Spread Parameter plugin</a></li>
<li><a href="http://WordPress.org/extend/plugins/yd-export2email/" rel="ugc">YD Export2Email plugin</a></li>
<li><a href="http://WordPress.org/extend/plugins/wp-theme-switcher/" rel="ugc">WP Theme Switcher plugin</a></li>
<li><a href="http://WordPress.org/extend/plugins/dj-email-publish/" rel="ugc">DJ E-mail Publish plugin</a></li>
<li><a href="http://wprobot.net/" rel="nofollow ugc">WPRobot plugin</a> credentials and settings</li>
<li><a href="http://WordPress.org/extend/plugins/easy-privacy-policy/" rel="ugc">Easy Privacy Policy plugin</a></li>
<li><a href="http://wpmu.org/plugin-commander-111/" rel="nofollow ugc">WordPress plugin Commander</a> to centrally activate or de-activate plugins network-wide</li>
<li><a href="http://wpml.org/" rel="nofollow ugc">WPML Multilingual CMS</a> (new since version 4.0.0)</li>
<li>and many, many more…</li>
</ul>
Only some plugins that do not use either WordPress’ built-in options mechanism or some simple database tables to store their settings cannot be made network-wide with this plugin. 
However, the vast majority of state-of-the art third-party plugins use options and/or simple tables.
Please leave a comment on the <a href="http://www.yann.com/en/wp-plugins/yd-wpmu-sitewide-options" title="Yann Dubois' Network-wide options plugin for multisite WordPress" rel="nofollow ugc">support site</a> to report 
other successful implementations, or any incompatibility.
<h4>Active support</h4>
Drop me a line on my <a href="http://www.yann.com/en/wp-plugins/yd-wpmu-sitewide-options" title="Yann Dubois' Network-wide options plugin for multisite WordPress" rel="nofollow ugc">WordPress developer site</a> to report bugs, ask for a specific feature or improvement, or just tell me how you’re using the plugin.
<h4>Description en Français :</h4>
Ce plug-in pour WordPress 3.0x multi-site ou WordPress MU permet de recopier automatiquement n’importe quel paramétrage (option, réglage) de plugin sur tous les blogs de votre réseau WordPress 3.0x ou WPMU. 
Toute modification (mise à jour) faite sur un paramètre sélectionné dans le blog principal peut être automatiquement répercutée sur les sous-blogs. 
De cette façon, vous pouvez centraliser la gestion de vos plugins transversaux.
Avec cette technique, n’importe quel plugin WordPress standard peut être converti en un plugin transversal pour WP3.0x multisite ou WPMU !
Les réglages de vos plugins sont automatiquement déployés sur tous vos sites WP MU ou sur tous les sites de votre réseau multi-sites.
Très pratique si vous installez un plugin transversalement (network-wide) sur tous vos blogs.
Le plugin a sa propre page d’options dans l’administration. 
Il est entièrement internationalisé.
La distribution standard inclut le fichier de traduction .pot et les versions française, anglaise, hollandaise et allemande.
Le plugin peut fonctionner avec n’importe quelle langue ou jeu de caractères.
Pour toute aide ou information en français, laissez-moi un commentaire sur le <a href="http://www.yann.com/en/wp-plugins/yd-wpmu-sitewide-options" title="Yann Dubois' Network-wide Options for multisite WordPress" rel="nofollow ugc">site de support du plugin YD WPMU Network-wide Options</a>.
Yann dubois, <a href="http://www.yann.com/fr/a-propos/developpeur-wordpress" title="Développeur WordPress freelance à Paris" rel="nofollow ugc">Développeur WordPress</a>.
<h4>Funding Credits</h4>
Original development of this plugin has been paid for by <a href="http://www.wellcom.fr" title="Wellcom" rel="nofollow ugc">Wellcom.fr</a>. Please visit their site!
Additional development was paid for by <a href="http://bossinternetmarketing.com/" title="bossinternetmarketing.com" rel="nofollow ugc">Matt Hardy</a>. Please visit his site!
Additional development was paid for by <a href="http://www.eurospreed.com/" title="Eurospreed.com" rel="nofollow ugc">Eurospreed</a>. Please visit their site!
Le développement d’origine de ce plugin a été financé par <a href="http://www.wellcom.fr" title="Wellcom" rel="nofollow ugc">Wellcom.fr</a>. Allez visiter leur site !
Des développements additionnels ont été financés par <a href="http://bossinternetmarketing.com/" title="bossinternetmarketing.com" rel="nofollow ugc">Matt Hardy</a>. Allez visiter son site!
<h4>Translation</h4>
If you want to contribute to a translation of this plugin, please drop me a line by e-mail or leave a comment on the <a href="http://www.yann.com/en/wp-plugins/yd-wpmu-sitewide-options" title="Yann Dubois' Network-wide Options plugin for multisite WordPress" rel="nofollow ugc">plugin’s page</a>. 
You will get credit for your translation in the plugin file and this documentation, as well as a link on this page and on <a href="http://www.yann.com/" rel="nofollow ugc">my developers’ blog</a>.
Dutch version kindly provided by <a href="http://www.fethiyehotels.com" rel="nofollow ugc">Rene</a>
German version kindly provided by <a href="http://www.pangaea.nl/diensten/exact-webshop" rel="nofollow ugc">Rian</a>
<h3>Plugin settings/options page</h3>
Use the plugin’s own settings page to select which plugin options/settings to automatically replicate network-wide / site-wide.
<h3>Revisions</h3>
<ul>
<li>0.1.0 Original beta version.</li>
<li>0.1.1 Optional debug code.</li>
<li>0.2.0 Bugfixes + improved settings page.</li>
<li>1.0.0 Bugfixes + important new features.</li>
<li>1.1.0 Bugfixes + new features.* 1.1.</li>
<li>1.1.1 Bugfix</li>
<li>3.0 WordPress 3.0 compatibility</li>
<li>3.0.1 Minor text changes</li>
<li>4.0.0 Database table replication, bugfixes, flush rewrite rules, choose master, ignore blogs</li>
</ul>
<h3>Did you like it?</h3>
Drop me a line on http://www.yann.com/en/wp-plugins/yd-wpmu-sitewide-options
And… please rate this plugin –>

YD Network-wide Options

This plugin has been thoroughly tested and is fully compatible with WordPress 3.0x multisite or with WPMU 2.9.

Van Patten Media

Ensures logins are always done via SSL on a subdomain of the master domain, but that access to custom domains are always done over HTTP, to avoid certificate errors. For WordPress Multisite.
WordPress’ built-in <code>FORCE_SSL_LOGIN</code> and <code>FORCE_SSL_ADMIN</code> directives in <code>wp-config.php</code> work great, but are too restrictive in situations where you have custom domains — custom domains for which you cannot have SSL certificates. For sites on custom domains, we need to make sure that the login and admin access happens over the subdomain, which can be properly served over HTTPS.
<h4>What this Plugin does (incorporating Foolish Assumptions)</h4>
or, a readme you should read before implementing this plugin on your site.
This plugin filters the login, logout, home and admin URLs that WordPress uses to generate its internal links.
Why do we do this?
<h4>The Scenario</h4>
We have a WordPress Multisite network. Let’s call it <code>mynetwork.com</code>. We bought a fancy SSL wildcard certificate so we can offer <code>*.mynetwork.com</code> over a secure connection.
We’d very much like to use this secure connection for all logins, and for all admin access.
We also allow sites on this network to use a custom domain — like <code>demo-site.com</code>. We might be using <a href="https://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/" rel="ugc">WPMU Domain Mapping</a> to achieve this. These sites have two domains, then — <code>demo-site.com</code> and <code>demo-site.mynetwork.com</code>.
If we switch on <code>FORCE_SSL_LOGIN</code> or <code>FORCE_SSL_ADMIN</code>, we have a problem. When users go to <code>https://demo-site.com/wp-login.php</code>, they get a certificate error. We have a wildcard certificate for <code>*.mynetwork.com</code>, but we can’t possibly have a valid SSL certificate installed for every custom domain!
Instead, we want to force all login pages and admin pages to be:
<pre><code>https://demo-site.mynetwork.com/wp-admin/… </code></pre>
We want all regular access to be:
<pre><code>http://demo-site.com/… </code></pre>
This plugin facilitates that — rewriting the <code>wp-login</code> (including logout) and <code>wp-admin</code> URLs to the first example, and rewriting all the others to the second style.
<h4>Foolish Assumptions</h4>
This plugin makes some (foolish) assumptions about your multisite network. You must make sure that these assumptions are true for your site, or you will find that this plugin may have unintended consequences and break things that are difficult to fix without manually disabling the plugin.
<ol>
<li>
Your subdomains are in the format: <code>a.b</code>
<blockquote>
where <code>a</code> is, for example: <code>demo-site</code>. <code>b</code> is, for example: <code>mynetwork.com</code>. <code>a</code> must be a single domain component. (<code>a</code> can’t be, for example: <code>demo.site</code>)
</blockquote>
</li>
<li>
Your wildcard certificate is configured properly for:
<ul>
<li><code>*.mynetwork.com</code></li>
<li>your network site URL</li>
</ul>
So if your network site URL is <code>www.mynetwork.com</code>, your wildcard cert will be fine. If it is just <code>mynetwork.com</code>, you will need another cert to avoid errors when you go to <code>https://mynetwork.com/wp-admin</code>.)
</li>
<li>
Your site already has the custom domains working.
<ul>
<li>
I suggest the excellent <a href="https://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/" rel="ugc">WPMU Domain Mapping</a> for this.
<ul>
<li>Your web server also needs to be <a href="http://www.lampjunkie.com/2008/05/how-to-set-up-a-wildcard-catch-all-virtual-host-in-apache/" title="A tutorial on wildcard catch all hosting for Apache" rel="nofollow ugc">set up</a> to handle hosting a wildcard name virtual host. All of this is really part of the WPMU Domain Mapping set up, and not the set up for this plugin. I’m just, you know, mentioning it.</li>
</ul>
</li>
</ul>
</li>
<li>
You have the <code>FORCE_SSL_LOGIN</code> setting in <code>wp-config.php</code> true.
</li>
<li>
You have the <code>FORCE_SSL_ADMIN</code> setting in <code>wp-config.php</code> false. We’ll handle that — WordPress’ forcing of SSL admins will conflict with this plugin.
</li>
</ol>

SSL Subdomain for Multisite

Ensures logins are always done via SSL on a subdomain of the master domain, but access to custom domains are always over HTTP, to avoid cert errors.

YD Network-wide Options vs SSL Subdomain for Multisite