mvied

I see you have the plugin in debug mode, and if you look, it says “SSL: No” on HTTPS pages, which means something is not configured correctly. Generally this is caused by your web server being hosted through a proxy and the proxy not setting the correct headers. The issue is definitely your web host’s configuration.

Hmm. No, it should just work. Let me set up a test similar to your setup and I’ll see if I can reproduce the issue. Or, if you can give me FTP and admin access, I’m sure I could figure out exactly what’s going on. My email is mike[at]mvied[dot]com.

Yes, it always uses 301 redirects.

You can find all previous versions here.

Could you check your Apache error logs for the error produced so that I can look into a fix? I do not have this issue.

That’s a pain. Don’t do that. You can use a piece of code in your theme’s functions.php (or in a custom plugin). Change ‘5’ to the ID of the post you don’t want to be secure.

function custom_force_ssl( $force_ssl, $post_id = 0, $url = '' ) {
    if ( $post_id == 5 ) {
        $force_ssl = false;
    } else {
        $force_ssl = true;
    }
    return $force_ssl;
}

add_filter('force_ssl' , 'custom_force_ssl', 10, 3);

The issue is the plugin is querying URL’s to see if the URL’s map to pages. Each check is query. The more URL’s on your pages, the more queries there are. I am looking for ways to cache results or something, but it’s not an easy problem to solve.

It’s not a bug. I will consider creating a “Lite” version.