Topic-icon No Linkedin buttons on site pages after migration to JFBCv6.0.6

Active Subscriptions:

None
Are we incorrect in assuming the Linkedin button should now be appearing on our site pages after migration to JFBCv6.0.6?

We've followed the recommended migration path, AutoTune shows all GREEN items. We have verified the Linkedin Developer OAuth2 redirect URL's per the recommended steps, too. We have also followed SC steps to remove the previous JLinked component, but have not deleted the final files until we are sure everything is working correctly.

What are we missing?
Thanks in advance! :=D

File Attachment:


File Attachment:
The topic has been locked.
Support Specialist
In the Javascript API Domains, you have both the www and non-www domain set. However, both of those are using http:// When I go to your site, I'm always redirected to https.

Can you update the 2 domains you've set in the Javascript API Domains to use https? I think that should be all you need, but if that doesn't work, let us know and we'll gladly help investigate further.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
Alex -

Changed the JavaScript API Domains settings as instructed...still not seeing the Linkedin button of the site pages. (see updated app settings, fyi).

File Attachment:
The topic has been locked.
Support Specialist
You're running into what is, by-far, the most nitpicking setting of any of the social networks. That value for the Javascript API Domains must be comma-separated with no carriage returns. It's similar to the OAuth2 Redirection URL setting above it. Update the Javascript API Domain setting to:
https://graysonallen.com,https://www.graysonallen.com

I hope that helps, and sorry I missed that issue before.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
SOLVED. Thank you. However, just FYI...other sites we have developed still have their Linkedin API settings unchanged and there seems to be no issues with losing the Linkedin Share button. All these sites we use the same force-redirect to https://, too. ...not sure why this is, but will keep an eye on those.
The topic has been locked.
Support Specialist
Not sure either. LinkedIn is really picky with some of their settings and they change how things work, without much notice, here and there. It's very reminiscent of Facebook early on with their API. Fortunately, Facebook and even LinkedIn are much more 'stable' than they used to be.

I'm glad it's working for you now. The suggestions above are definitely what you *should* be using, so even if the other sites work, it's best to perform the same changes to their settings if they don't have all URL variations or aren't using a comma-separated list.

Of course, if you run into anything else or need more assistance, just let me know.

Thanks,
Alex
The topic has been locked.