Comments on: Securing a WordPress Page with SSL http://mccormicky.com/1297/securing-a-wordpress-page-with-ssl/ Freelance Web Designer Fri, 18 Nov 2011 12:17:43 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jesse http://mccormicky.com/1297/securing-a-wordpress-page-with-ssl/comment-page-1/#comment-25912 Jesse Fri, 24 Sep 2010 21:37:43 +0000 http://mccormicky.com/?p=1297#comment-25912 Thank you for sharing this. I was afraid I was going to have to meddle some more in other people's plugins. I'll report back my success/failures for others. Thank you for sharing this. I was afraid I was going to have to meddle some more in other people’s plugins. I’ll report back my success/failures for others.

]]> By: Dixie Vogel http://mccormicky.com/1297/securing-a-wordpress-page-with-ssl/comment-page-1/#comment-13160 Dixie Vogel Wed, 24 Feb 2010 15:08:53 +0000 http://mccormicky.com/?p=1297#comment-13160 I've been researching this issue myself as I need to secure a couple pages in a WP install. You all may be interested in this article I found on it, where he provides a workaround for the mixed content error - http://www.propellingsolutions.com/2009/12/securing-a-wordpress-page-with-https/ Haven't tested it yet but I will be, I'm sure... :) I’ve been researching this issue myself as I need to secure a couple pages in a WP install. You all may be interested in this article I found on it, where he provides a workaround for the mixed content error – http://www.propellingsolutions.com/2009/12/securing-a-wordpress-page-with-https/

Haven’t tested it yet but I will be, I’m sure… :)

]]> By: mccormicky http://mccormicky.com/1297/securing-a-wordpress-page-with-ssl/comment-page-1/#comment-11447 mccormicky Mon, 01 Feb 2010 01:27:04 +0000 http://mccormicky.com/?p=1297#comment-11447 Yes, I have been able to secure just one WordPress page-but if you read this post you'll see it takes a bit of work-especially if you use plugins whose javascript and css files don't get switched to https:// in your wordpress theme header.php or footer.php. Plugins files are the number 1 reason I've ever had a problem securing a WordPress page. All JavaScript and css files must be linked to with https:// not http:// or the secure page will throw a warning that the page contains secure and insecure items. And this goes for image files as well. Get the HTTPS for WordPress plugin, upload it and activate it and then go to any page on your site using a https:// URL, example https://www.mysite.com/my-secure-page/. If you use Permalinks. If you don't have Permalinks turned on the link will look like this : https://www.mysite.com/?=23. In Internet Explorer if the webpage is secured and there are no insecure items and the SSL certificate is valid you will see a lock icon next to your addressbar. In Firefox the addressbar will turn blue. If the lock icon has a jagged line through it and you get a warning that the page has insecure items(Internet Explorer) or the addressbar starts out as blue then goes back to white(Firefox) then you have to view the source of the page and see which files have link rel="https:// or just link rel="http://. Like I said earlier the culprits are usually JavaScript or CSS files needed by plugins you are using or images you've embedded in the page. One thing you can do is turn off all other plugins except HTTPS for WordPress plugin and then see if the page loads securely without issues. Then keep turning plugins back on one by one until you find the one that is not getting its files secured. If you follow the tutorial here you'll see what I suggest doing. Its not exactly easy as pie but so far its the only way I've been able to find to secure just one page, not the whole site. Yes, I have been able to secure just one WordPress page-but if you read this post you’ll see it takes a bit of work-especially if you use plugins whose javascript and css files don’t get switched to https:// in your wordpress theme header.php or footer.php. Plugins files are the number 1 reason I’ve ever had a problem securing a WordPress page. All JavaScript and css files must be linked to with https:// not http:// or the secure page will throw a warning that the page contains secure and insecure items. And this goes for image files as well.
Get the HTTPS for WordPress plugin, upload it and activate it and then go to any page on your site using a https:// URL, example https://www.mysite.com/my-secure-page/. If you use Permalinks.
If you don’t have Permalinks turned on the link will look like this : https://www.mysite.com/?=23. In Internet Explorer if the webpage is secured and there are no insecure items and the SSL certificate is valid you will see a lock icon next to your addressbar. In Firefox the addressbar will turn blue. If the lock icon has a jagged line through it and you get a warning that the page has insecure items(Internet Explorer) or the addressbar starts out as blue then goes back to white(Firefox) then you have to view the source of the page and see which files have link rel=”https:// or just link rel=”http://. Like I said earlier the culprits are usually JavaScript or CSS files needed by plugins you are using or images you’ve embedded in the page.
One thing you can do is turn off all other plugins except HTTPS for WordPress plugin and then see if the page loads securely without issues. Then keep turning plugins back on one by one until you find the one that is not getting its files secured.
If you follow the tutorial here you’ll see what I suggest doing. Its not exactly easy as pie but so far its the only way I’ve been able to find to secure just one page, not the whole site.

]]> By: Karen http://mccormicky.com/1297/securing-a-wordpress-page-with-ssl/comment-page-1/#comment-11440 Karen Sun, 31 Jan 2010 20:56:20 +0000 http://mccormicky.com/?p=1297#comment-11440 Have you ever been able to force SSL on only one page in a Wordpress site? We have a donations page that needs SSL but do not want SSL on the rest of the site. Have you ever been able to force SSL on only one page in a WordPress site? We have a donations page that needs SSL but do not want SSL on the rest of the site.

]]>