Hi Dan,
I’ll double check my live site to make sure LinkedIn is still working in the latest version. Other than that I’d say make sure to double check that your Redirect URLs match, and that you’re satisfying the conditions in the LinkedIn instructions (on the plugin settings page). I’ll let you know if I need more details.
Wow – fast response! Thanks!
I may still be looking over something, but here is what I checked:
- Registered with API Key and Secret Key
- Plugin LinkedIn directions, step 3, calls for me to use http://mydomain.net/ as the App’s Redirect URI
- Linkedin API has http://mydomain.net/ (with trailing slash) in 3 spots: OAuth 2.0 Redirect URLs, OAuth 1.0a Accept Redirect URL, and OAuth 1.0a Accept Redirect URL
- Attempted with app “* Live Status:” set to both Live and Development
Again thank you for your time and help. Really appreciate it!
I’m having this issue with LinkedIn as well. It looks like their API may have changed recently. Will keep you posted…
Have you tried setting the HTTP utility to Stream Context? That appears to be working for me, and I think I see the problem affecting cURL now…
And that fixed it. Huge Help.
Cheers!
LinkedIn made some unannounced changes to their API this week which seems to have broken many cURL implementations across the web.
https://stackoverflow.com/questions/29503312/linkedin-api-suddenly-returning-405-error
Go ahead and use Stream Context for now until I hear official word on these changes, or until I roll out a cURL fix in the next version.
