Yann at WP&amp;Co

<p>This plugin is an add-on to the <a href="http://wpml.org/" rel="nofollow ugc">WPML Multilingual CMS plugin</a> from http://wpml.org.</p>
<p>It is also an add-on to the <a href="http://ocaoimh.ie/wordpress-mu-sitewide-tags/" title="WordPress MU Sitewide Tags Pages plugin from Donncha O Coimh" rel="nofollow ugc">WordPress MU Sitewide Tags Pages plugin from Donncha O Coimh</a> (aka. SWT).</p>
<p>It will make it possible to have site-wide contents, search, tags and categories in multiple languages.</p>
<h4>Network-wide multilingual support</h4>
<p>This WordPress 3.0 multisite or WPMU plugin makes sure that all data replicated to a central aggregation blog by the WordPress MU Sitewide Tags Pages plugin keeps its language properties generated by the WPML Multilingual CMS plugin.</p>
<p>Base package includes .pot file for translation of the interface, and English and French versions.</p>
<h4>Installing WPML Network-wide</h4>
<p>You will need my other plugin <a href="https://wordpress.org/extend/plugins/yd-wpmu-sitewide-options/" rel="ugc">YD Network-wide Options</a> to automatically install and setup WPML on all sub-blogs and replicate settings changes on all blogs.</p>
<h4>Beta</h4>
<p>This plugin is still in development stage / beta version. But the main features are already working.</p>
<h4>Active support</h4>
<p>Drop me a line on my <a href="http://www.yann.com/en/wp-plugins/yd-network-wide-wpml" title="Yann Dubois' Network-wide WPML 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.</p>
<h4>Description en Français :</h4>
<p>Cette extension pour WordPress 3.0x multi-site ou WordPress MU permet de recopier automatiquement les propriétés linguistiques des articles quand ils sont répliqués dans le blog d’agrégation de l’extension WordPress MU Sitewide Tags depuis tous les blogs de votre réseau WordPress 3.0x ou WPMU.</p>
<p>On obtient ainsi un réseau de sites multilingues, avec possibilité d’avoir des mots-clés (tags), des catégories ou une recherche transversales.</p>
<p>Cette extension est entièrement internationalisée.</p>
<p>La distribution standard inclut le fichier de traduction .pot et les versions française et anglaise.</p>
<p>Le plugin peut fonctionner avec n’importe quelle langue ou jeu de caractères.</p>
<p>Pour toute aide ou information en français, laissez-moi un commentaire sur le <a href="http://www.yann.com/en/wp-plugins/yd-network-wide-wpml" title="Yann Dubois' Network-wide WPML for multisite WordPress" rel="nofollow ugc">site de support du plugin YD Network-wide WPML</a>.</p>
<p>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>.</p>
<h4>Funding Credits</h4>
<p>Original development of this plugin has been paid for by <a href="http://www.wellcom.fr" title="Wellcom" rel="nofollow ugc">Wellcom</a>. Please visit their site!</p>
<p>Le développement d’origine de ce plugin a été financé par <a href="http://www.wellcom.fr" title="Wellcom" rel="nofollow ugc">Wellcom</a>. Allez visiter leur site !</p>
<h4>Translation</h4>
<p>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-network-wide-wpml" title="Yann Dubois' Network-wide WPML plugin for multisite WordPress" rel="nofollow ugc">plugin’s page</a>.<br />
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 WordPress developers’ blog</a>.</p>
<h3>Revisions</h3>
<ul>
<li>0.1.0 Original beta version.</li>
<li>0.1.1 Improved beta version.</li>
<li>0.1.2 Improved beta version.</li>
<li>0.1.3 Improved beta version.</li>
</ul>
<h3>Did you like it?</h3>
<p>Drop me a line on http://www.yann.com/en/wp-plugins/yd-network-wide-wpml</p>
<p>And… <em>please</em> rate this plugin –></p>


YD Network-wide WPML

Add-on to WPML and to WPMU Sitewide tags plugins. Will propagate WPML language properties to the Network wide aggregation blog.

Van Patten Media

<p>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.</p>
<p>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.</p>
<h4>What this Plugin does (incorporating Foolish Assumptions)</h4>
<p><em>or, a readme you <strong>should</strong> read before implementing this plugin on your site.</em></p>
<p>This plugin filters the login, logout, home and admin URLs that WordPress uses to generate its internal links.</p>
<p>Why do we do this?</p>
<h4>The Scenario</h4>
<p>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.</p>
<p>We’d very much like to use this secure connection for all logins, and for all admin access.</p>
<p>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>.</p>
<p>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!</p>
<p>Instead, we want to force all login pages and admin pages to be:</p>
<pre><code>https://demo-site.mynetwork.com/wp-admin/… </code></pre>
<p>We want all regular access to be:</p>
<pre><code>http://demo-site.com/… </code></pre>
<p>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.</p>
<h4>Foolish Assumptions</h4>
<p>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.</p>
<ol>
<li>
<p>Your subdomains are in the format: <code>a.b</code></p>
<blockquote>
<p>where <code>a</code> is, for example: <code>demo-site</code>.   <code>b</code> is, for example: <code>mynetwork.com</code>.   <code>a</code> <strong>must</strong> be a single domain component. (<code>a</code> can’t be, for example: <code>demo.site</code>)</p>
</blockquote>
</li>
<li>
<p>Your wildcard certificate is configured properly for:</p>
<ul>
<li><code>*.mynetwork.com</code></li>
<li>your network site URL</li>
</ul>
<p>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>.)</p>
</li>
<li>
<p>Your site already has the custom domains working.</p>
<ul>
<li>
<p>I suggest the excellent <a href="https://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/" rel="ugc">WPMU Domain Mapping</a> for this.</p>
<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>
<p>You have the <code>FORCE_SSL_LOGIN</code> setting in <code>wp-config.php</code> <strong>true</strong>.</p>
</li>
<li>
<p>You have the <code>FORCE_SSL_ADMIN</code> setting in <code>wp-config.php</code> <strong>false</strong>. We’ll handle that — WordPress’ forcing of SSL admins will conflict with this plugin.</p>
</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 WPML vs SSL Subdomain for Multisite