mvied

I pushed out 3.0.4 today which should fix the issues you guys were having with securing your entire site.

If someone is using a service like CloudFlare or some other caching mechanism, pulling HTTPS resources on the HTTP page may prevent those caching services from working correctly.

There is no reason for the plugin to change a random URL in JavaScript. Is the JS you posted hard-coded, or are you using WordPress functions to pull the site’s URL?

If you want to make your whole site HTTPS, change your Site URL to contain HTTPS.

Currently the only option for mass-updating posts is writing some custom code to do so.

$args = array(
	'numberposts' => -1
);
$posts = get_posts($args);
foreach( $posts as $post ) {
	update_post_meta($post->ID, 'force_ssl', '1');
}

So you want to secure all links for logged in users?

You could do that pretty easily by adding this to your theme’s functions.php:

function logged_in_force_ssl( $force_ssl, $post_id ) {
    if ( is_user_logged_in() ) {
        $force_ssl = true;
    }
    return $force_ssl;
}
add_filter('force_ssl', 'logged_in_force_ssl', 10, 2);

It may not work perfectly. Let me know.

To my knowledge, there is no way around this. The proxy sitting in front of the server hosting WordPress is not properly passing the Request URI so WordPress doesn’t know where to send the user (it can’t even pull up the front page). Unfortunately, this is caused by a proxy not being configured correctly, but sometimes it is intentional by the hosting company because they do not want you using the Shared SSL certificate with WordPress or anything like that.

That’s what I’ve learned from talking to users of my plugin that have run into this issue.

Can you look at the code that creates the form? Perhaps it’s hard-coded.

Uninstall/delete the plugin and re-install. If the problem persists, please provide as much detail as possible. Your configuration, what error you receive, what you’ve tried to fix the issue, etc. “Crashed website” is not enough information to help you.