• GetSocial includes assets from Facebook, Twitter, Google, etc. using http:// instead of https://. This causes a lot of functionality to break if it’s running on a WordPress site hosted on https.

    I’ve manually replaced the necessary http:// with https:// in getsocial.php, but it would be nice to incorporate this in a future release (or even better, intelligent selection of URI scheme based on the current page).

    https://wordpress.org/plugins/getsocial/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hey Walter,

    Any chance you might be able to send me your updated version of the getsocial.php? I’ve just upgraded my site to https:// and it’s causing this plugin a lot of problems.

    Thanks, James

    Thread Starter walterlp

    (@walterlp)

    Just open getsocial.php in your editor and replace every occurrence of http:// to https://

    Thanks for the quick response. I had already tried that though, and I noticed a couple of weird things…

    1. The counts for Facebook and Twitter have been reset to 0, whereas G+ still has the same number of likes that it did before I upgraded to https:// (not 0).

    2. StumbleUpon just isn’t loading properly. Instead there’s a bit of bulletpointed text which doesn’t fit in the box.

    I just wondered whether you’d found ways around these problems? I’m not too bothered about the second one, but the loss of Facebook likes is annoying.

    Thread Starter walterlp

    (@walterlp)

    We’ve been using HTTPS from day 1, so we didn’t have the problem of counts being reset. They are incrementing just fine for us.

    I didn’t include StumbleUpon, so don’t know about that one!

    The Twitter count will not reset if you only https the javascript file.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Does not support SSL’ is closed to new replies.