Plugin Author
thhake
(@thhake)
Just out of curiosity, what kind of error messages are you getting?
I was already thinking about making https the default, but in my internal tests the loading times for a page with a lot of albums increased a lot compared to http (for each album one http(s) connection to google photo gets eastablished and closed, which is far more “expensive” for https connections). In one of the upcoming versions I’ll include an internal caching feature that will cache the answers from the google photo api, so that page rendering will be way faster no matter if you are using https or http. After I have implemented this caching feature, making https a default wouldn’t harm anyone anymore.
For now you can simply change http to https in you shorttags. It should work without a problem.
Mixed Content: The page at ‘https://lawchristopher.com/london-tower-of-london/’ was loaded over HTTPS, but requested an insecure image ‘http://lh3.googleusercontent.com/-6RWIWDpM_V0/UcDD84L4ovI/AAAAAAAAFt0/hXXr_qt_nnM/s1000/IMG_8300.jpg’. This content should also be served over HTTPS.
Here’s an example. Basically happens when clicking/fetching the image. Ah, but your suggestion does work. Didn’t realize that’s where it was getting it from haha but it would be nice if it was automatic.
Plugin Author
thhake
(@thhake)
I’ve included a “force SSL” switch in the newest development edition (on github). It should suite your needs. The switch is on by default.
It seems to work 🙂 Looks pretty good. No warnings or errors now.
