Hassan1

WPMU Custom CSS is a plugin for wordpress mu that helps bloggers to edit their theme style securely. Just like wordpress.com custom css paid upgrade. 
Site admin can enable this feature for all or specific blogs (e.g. premium members).
It also integrated with our membership plugin <a href="http://wpwave.com/plugins/cms-members/" rel="nofollow ugc">CMS Members MU</a>
<h3>Installation WordPress MU</h3>
While doing the installation procedure, it is recommended to go through all the steps first before viewing the output. If you don’t, you’ll get nasty error messages.
<ol>
<li>Upload <code>wpmu-custom-css.php</code> into the <code>/wp-content/mu-plugins</code> directory</li>
</ol>
—wp-content/mu-plugin/wpmu-custom-css.php
<ol>
<li>That’s all. </li>
</ol>
Now take a look at Site Admin -> Options menu
<h3>Upgarde to new versions</h3>
To upgrade WPMU Custom CSS simply delete old files and then install new version.

WPMU Custom CSS

WPMU Custom CSS is a plugin for wordpress mu that helps bloggers to edit their theme style securely. Just like wordpress.com custom css paid upgrade.

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.

WPMU Custom CSS vs SSL Subdomain for Multisite