Forces all logged in users to stay on SSL connection. Guests are still served http. 
Just install and activate – all done!
<ul>
<li>NOTE: The ‘force_ssl_admin’ and ‘force_ssl_login’ directives in ‘wp-config.php’ are not needed while using this plugin.</li>
</ul>
<h3>Features</h3>
<ul>
<li>SSL Login</li>
<li>SSL enforced for entire logged-in session</li>
<li>SSL for Admin and front-end of site</li>
<li>No messing with ‘wp-config.php’ or ‘htaccess’ directives</li>
<li>Easy to use, just install and activate on any SSL equipped site – no configuration required</li>
<li>WordPress 3.5 compatible</li>
<li>Network/Multisite compatible – can be activated on any sites in the Network, individually – sites should have a valid SSL certificate</li>
<li>Buddypress compatible</li>
<li>WP-Super-Cache compatible</li>
<li>S2Member compatible</li>
<li>Bulletproof Security compatible</li>
<li>The ‘force_ssl_admin’ and ‘force_ssl_login’ directives in ‘wp-config.php’ are not needed while using this plugin.</li>
</ul>

SSL for Logged In Users

Forces all logged in users to stay on SSL connection

Steve85b

Try it out on your free dummy site: Click here => <a href="https://tastewp.com/plugins/http-https-remover" rel="nofollow ugc">https://tastewp.com/plugins/http-https-remover</a>. 
(this trick works for all plugins in the WP repo – just replace “wordpress” with “tastewp” in the URL)
UPDATE: This plugin will be maintained again! It changed ownership and we’re currently collecting ideas how to further improve it. If you have any cool ideas, please let us know in Support Forum. Thank you!
Major updated in the latest release (3.0): 
– Plugin has a proper settings page now 
– Many bugs fixed 
– Code optimized, causing performance to increase a lot
Main features:
<ul>
<li>Works in Front- and Backend</li>
<li>Makes every Plugin compatible with https</li>
<li>Compatible with WPBakery & Disqus</li>
<li>Fixes Google Fonts issues</li>
<li>Makes your website faster</li>
</ul>
<h4>What does this Plugin do?</h4>
With protocol relative url’s you simply leave off the http: or https: part of the resource path. The browser will automatically load the resource using the same protocol that the page was loaded with.
For example, an absolute url may look like
<pre><code>src="http://domain.com/script.js"
</code></pre>
If you were to load this from a https page the script will not be loaded – as non-https resources are not loaded from https pages (for security reasons).
The protocol relative url would look like
<pre><code>src="//domain.com/script.js"
</code></pre>
and would load if the web page was http or https.
Tipp: Check your Settings -> General page and make sure your WordPress Address and Site Address are starting with “https”. 
Add the following two lines in your wp-config.php above the line that​ says “Stop Editing Here”:
<pre><code>define('FORCE_SSL', true);
define('FORCE_SSL_ADMIN',true);
</code></pre>
<h4>What is Mixed Content?</h4>
Mixed content occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS. Modern browsers display warnings about this type of content to indicate to the user that this page contains insecure resources.
Note: You should always protect all of your websites with HTTPS, even if they don’t handle sensitive communications.
<h4>Example</h4>
Without Plugin: 
 src=”http://domain.com/script01.js” 
 src=”https://domain.com/script02.js” 
 src=”//domain.com/script03.js”
With Plugin: 
 src=”//domain.com/script01.js” 
 src=”//domain.com/script02.js” 
 src=”//domain.com/script03.js”
<h4>If using Cache Plugins</h4>
If the plugin isn’t working like expected please purge/clear cache for the changes to take effect!

SSL Mixed Content Fix

This is really simple plugin and easy to configure. It works fine and really useful.

Awesome Plugin

A fix for mixed content! This Plugin creates protocol relative urls by removing http + https from links. Works in Front- and Backend!

SSL for Logged In Users vs SSL Mixed Content Fix