Welcome

High quality MyBB plugins at your disposal

Hi, I am a passionate developer with modernity and simplicity in mind. MyBBoost is my mansion where you can download my plugins and themes, other than receiving support for them. Several free plugins are available as well as premium ones, all compatible with the latest MyBB releases. You can purchase and download items singularly or purchase a lifetime subscription including a combination of premium plugins and:

  • Priority support
  • Future plugins access
  • Total refund if not satisfied 1
1 Terms and conditions apply. For more informations, read the EULA.

Non-secure avatar link when importing user's Facebook photo

Tecca Advanced 12 Sep 2016
#1
Hey there Shade,

Great plugins, and awesome site you've got set up here! One issue I've noticed with importing a user's photo from Facebook is if your site uses HTTPS, the image is linked via unsecure protocol and the browser gives a warning. I haven't tried importing from Twitter/Google+, but those potentially may do the same thing as well.

Just thought I'd post this here in case you weren't aware. FB does use secure images, though it's only redirected to HTTPS if you try to view the avatar in your browser (it gets redirected).
Shade Administrator 12 Sep 2016
#2
Thank you Tecca for your contribution. I have a MFC restyle in mind so this will help to build the next major version.
Grzeniu Regular user 28 Oct 2017
#3
Shade are you planning on implementing this function or, could you give a tip which file to modify to set the url to https instad of http for the new users? I can modify the old users' http via MySQL, but I'd rather have it use https from now on for new users.

My regards!
Greg
Shade Administrator 28 Oct 2017
#4
Hi Grzeniu, theoretically the latest version should already format avatars to use the HTTPS secure protocol. Can you provide your board URL where I can see eventual issues? Thank you.
Grzeniu likes this post
Grzeniu Regular user 28 Oct 2017
#5
Hello Shade Thank you for the quick reply! My apologies - I have version 3.1 installed. For some reason when I checked if I have the up-to-date version, I mistakenly saw that I have 3.2 - probably I have looked at some other plugin version, whereas I have the 3.1.

Thus, I will update to 3.2 and the issue will be gone.

Thank you for help and for maintaining such a fine plugin, my regards!
Shade Administrator 28 Oct 2017
#6
I have just checked and 3.2 fixes the issue, while 3.1 is affected. I would suggest you to use the current GitHub version as it includes a fix reported some time ago which may affect you too.
Grzeniu likes this post
  • 3 participants