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.

nkuttler

Switch between the backends of your WPMU blogs with just one click. This is probably only useful if you don’t have too many blogs and use all of them yourself. The switch links will be added to your super admin menu.
With the release of WordPress 3.0 I merged several WordPress installs into a single network-enabled WordPress 3.0 install. As I post on all of them I wanted the ability to switch quickly between the backends. This plugin makes that possible
By the way, I use the Ozh admin menu plugin. You might need two clicks to switch if you don’t.
<h4>Support</h4>
Visit the <a href="http://www.nkuttler.de/wordpress/" rel="nofollow ugc">plugin’s home page</a> to leave comments, ask questions, etc.
<h4>My plugins</h4>
<a href="http://www.nkuttler.de/2010/06/07/wpmu-switch-backend/" rel="nofollow ugc">MU fast backend switch</a>: Switch between your MU blog backends with one click
<a href="http://www.nkuttler.de/2010/05/21/record-movies-of-visitors/" rel="nofollow ugc">Visitor Movies for WordPress</a>: Did you ever want to know what your visitors are really doing on your site? Watch them!
<a href="http://www.nkuttler.de/wordpress/nktagcloud/" rel="nofollow ugc">Better tag cloud</a>: I was pretty unhappy with the default WordPress tag cloud widget. This one is more powerful and offers a list HTML markup that is consistent with most other widgets.
<a href="http://www.nkuttler.de/wordpress/nkthemeswitch/" rel="nofollow ugc">Theme switch</a>: I like to tweak my main theme that I use on a variety of blogs. If you have ever done this you know how annoying it can be to break things for visitors of your blog. This plugin allows you to use a different theme than the one used for your visitors when you are logged in.
<a href="http://www.nkuttler.de/wordpress/zero-conf-mail/" rel="nofollow ugc">Zero Conf Mail</a>: Simple mail contact form, the way I like it. No ajax, no bloat. No configuration necessary, but possible.
<a href="http://www.nkuttler.de/wordpress/custom-avatars-for-comments/" rel="nofollow ugc">Custom avatars for comments</a>: Add a personal touch: Your visitors will be able to choose from the avatars you upload to your website for each and every comment they make.
<a href="http://www.nkuttler.de/wordpress/nkmovecomments/" rel="nofollow ugc">Move WordPress comments</a>: This plugin adds a small form to every comment on your blog. The form is only added for admins and allows you to <a href="http://www.nkuttler.de/nkmovecomments/" rel="nofollow ugc">move comments</a> to a different post/page and to fix comment threading.
<a href="http://www.nkuttler.de/wordpress/delete-pending-comments" rel="nofollow ugc">Delete Pending Comments</a>: This is a plugin that lets you delete all pending comments at once. Useful for spam victims.
<a href="http://www.nkuttler.de/wordpress/nksnow/" rel="nofollow ugc">Snow and more</a>: This one lets you see snowflakes, leaves, raindrops, balloons or custom images fall down or float upwards on your blog.
<a href="http://www.nkuttler.de/wordpress/nkfireworks/" rel="nofollow ugc">Fireworks</a>: The name says it all, see fireworks on your blog!
<a href="http://www.rhymebox.de/blog/rhymebox-widget/" rel="nofollow ugc">Rhyming widget</a>: I wrote a little online <a href="http://www.rhymebox.com/" rel="nofollow ugc">rhyming dictionary</a>. This is a widget to search it directly from one of your sidebars.

WPMU fast backend switch

Switch between the backends of your WPMU blogs with one click

SSL Subdomain for Multisite vs WPMU fast backend switch