Hi Badwood,
Could you please provide a link to where this is happening so that I may investigate further?
Thanks!
Hi Badwood,
I actually started doing my own testing on a fresh WordPress 3.0.1 installation with a page with only a Google Maps iframe on it and was unable to have the page load securely.
I went as far as to make modifications to the plugin that changed the iframe to HTTPS, but the frame itself continued to load insecure elements, so the page still gave encryption errors.
Unfortunately, that’s one of those things that is out of my control, and the plugin cannot fix them. I will have to add Google Maps to my list of limitations.
I did a little research about Google Maps over HTTPS, and apparently that functionality requires Google Maps API Premiere (source). If you must have the Google Map on your HTTPS page(s), I would suggest signing up for a Google Maps API Premiere account. You can do that here.
I hope that helps. 🙂
Hey thanks
Yeah we actually got contacted by Google. They charge a minimum of $10,000
for the Premiere account! It’s really crazy no one but the largest companies would
pay for that. I sent you an email back talking more about us and
what we do also with a link to the site. The thing I don’t get is why IE spits out a
warning and the other browsers don’t. I think it’s OK for the page to load insecure
but that IE warning really bites.
Is there anyway to turn off the ssl on this page only? So we can deactivate the ssl
only on that page and have it on the others maybe force https on all other pages but that
one. No sure really.
Hey Badwood,
Internet Explorer is actually the only browser that warns the user with an alert. Other browsers will show that the page is not completely secure, but won’t throw an error in the same way.
My recommendation is to not use HTTPS on the whole site, and only use it on pages that need to be encrypted such as pages with forms. The reason I say this is because the encryption process slows down the website considerably, and also takes its toll on your server’s resources.
However, if this is a requirement, I understand. You could have every page HTTPS except that one page by checking the ‘Force HTTPS’ checkbox (screenshot) on every page except that one and enabling the ‘Force SSL Exclusively’ option on the WordPress HTTPS Settings page. This would be pretty tedious, but for now it is the only way I can think of to do what you’re asking.
Thanks I think this might work. I will give it a try. How about the Home page where would I force HTTPS on that since it is not loaded as a page or post? Will it still stay as an https page. That’s the only thing I am not sure of. This is the first project that we have actually had to implement
https in more than one page but I know that you are not privy to how this site is built.
Hey Badwood,
This functionality will require modification to the plugin. I’m not 100% sure how I’m going to go about implementing this feature, but I have a few ideas. I should be able to get a new version out tonight, and I will update this topic when I have.
OK sounds good I will be around.
Hey Badwood,
I just wanted to give you an update. I’ve been quite busy this week and I’m heading to Texas for the weekend, but I’ll be back in the swing of things next week. I should have the new version out next week. It will include the changes to make your home page and posts pages forced to SSL as well as some other improvements. Sorry for the wait. 🙂
Hey yeah good to hear from you. Hey don’t forget the state fair is going on right now pretty
fun. Looking forward to your update. I am sure this will become a highly useful plugin for
wordpress. Have a good trip!
Yep, my wife and I are going to visit the Renaissance Festival. We usually go every year on opening weekend. The theme this weekend is Oktoberfest, yay! 😛
Hey Badwood,
WordPress HTTPS version 1.6 has been released. In the settings page I’ve added the ‘HTTPS Front Page’ option. If you are using latest posts for your front page, this option will be available. If you are using static pages, the option will not be shown and you can simply use the ‘Force SSL’ checkbox on your defined static pages to force them to HTTPS.
Enjoy!
Hey Your back hope you had a good time where is the Renaissance festival? Sounds like fun!
Is it scarbourough faire?
I accidentally didn’t update my post :p!
We loaded the update 1.6. We are having trouble With pages loading with force ssl not checked. We checked every page that should be ssl But the pages that are not checked spit out a page unable to load warning. We actually load the home page through the home and index pages but we do have posts to load certain elements on the home or index page. Let me know what you think maybe it’s how we built the site. 🙁 We have never set up ssl to load on certain pages and not on others. Due to the hosting environment we are restricted with testing. Let me know any ideas you have or if there is someway we can test the plugin to help you. It really is a great idea and a great plugin. Just to recap when we load the option force ssl and check every page that should be ssl the pages that are not checked spit out page unable to load warning.
I’ve updated your other topic. 😉 Let’s just take the conversation to the other topic since you’ve started a new one.
