For awhile now, my SSL certificate has been causing warnings for everyone who visits my site, likely driving many people away.
I was finally able to track down the cause of the issue and found that JFBConnect seems to be calling both the LinkedIn and Twitter platforms in an insecure manner.
Chrome developer tools logs the following warnings:
which I assume is being called by the sharing component in JFBConnect. However, I'm not sure if there's a configuration setting I'm missing, if there's no secure API for Twitter or LinkedIn, or if there's something missing within the code.
How would I temporarily disable the calling of this script?
Stylez,
Yup, we're always including the http version of the LinkedIn and Twitter scripts. To fix manually, in the /plugins/content/jfbccontent/jfbccontent.php file, around line 320, you'll fine the inclusion of those files (search for "linkedin.js" to get there quickly). Simply update the links to https.
I've taken note of this bug, and in the next release, we'll update it to automatically load the secure or non-secure script pages depending on the current page the user is on.
I searched for other http:// in jfbccontent.php and I found one reference to twitter, but nothing that might call the above image. So, where else can I look?
Alan,
That looks to be an issue with the LinkedIn share button. Although the Javascript library is now being loaded over https, it looks like it's including an image that itself is not being loaded securely. I don't think we can fix this, but are looking into possible alternatives.
Sorry for the troubles. We can help you disable just the LinkedIn button if you want, or you can disable all the social sharing buttons (for the time being). This bug looks to have been reported to LinkedIn multiple times since about April of this year, and it's in a "We're working on it" state.
There's not really a way for us to easily override the LinkedIn button's code, since that's loaded through their own Javascript. They actually do have a (tedious) workaround, that we're looking into, but we'd need to test it a bit first.
In the meantime, if the SSL issue is killing you, we'd recommend disabling just the LinkedIn button. To do that, you'll need to make a minor code modification, which you can see in the post below: www.sourcecoast.com/forums/jfbconnect/jf...en-button?p=1#p14280
Unsecure LinkedIn and Twitter platforms
