|
Watchman Monitoring
|
March 26, 2014 at 8:44 am
I see this using ee4 on the confirmation page
<code>The page at 'https://www.watchmanmonitoring.com/thank-you/?ee=launch_invoice&id=1-3a69e70d44e0a983e635038fdc4c8f05&html=1&receipt=true' was loaded over HTTPS, but displayed insecure content from 'http://maps.googleapis.com/maps/api/staticmap?center=225+Powell+Street%2CSa…l+Street%2CSan+Francisco%2CCalifornia%2C94102%2CUnited+States&sensor=false': this content should also be loaded over HTTPS.
</code>
can we get that to load over https please?
|
|
Lorenzo Orlando Caum
|
March 26, 2014 at 1:12 pm
Hello,
Could you try this plugin on your site?
https://wordpress.org/plugins/ssl-insecure-content-fixer/
—
Lorenzo
|
|
Watchman Monitoring
|
March 26, 2014 at 3:18 pm
There’s no telling what that’ll break/do. No I’m not interested in troubleshooting the fallout.
I just need you guys to put a S in the google maps call… kinda like that author put on the plugin’s readme?
I'll be adding other fixes as I find simple solutions for them. The better solution is to get errant plugins fixed by their authors, but until they do, let me know about them and I'll attempt to add fixes.
|
|
Tony
|
March 27, 2014 at 4:27 am
Hi,
I have issued a ticket for the developers to look into this.
As far as I am aware google maps require a little more than just specifying HTTPS so the developers will need to investigate this to find a working solution.
I’ll add a note to the ticket to update this thread with any findings
|
|
Watchman Monitoring
|
March 31, 2014 at 6:34 pm
Thanks
I also realize that this is the final page in the process, a lack of ssl isn’t a huge problem.
I’ll look at it again when I upgrade to ee4 later on.
|
