Forum Replies Created
- AuthorPosts
If you use %SURL% then there is no need to check it.
April 30, 2015 at 4:08 pm in reply to: Error posting to LinkedIn personal pages but not company pages #419299LauraVM
ParticipantOK. I had typed a URL wrong for the new site I was setting up. So the company page for that site works. But I still can’t get the posts to personal pages to work. I’m not sure what you mean when you say, “Please use LinkedIn APi, not Nextscripts APi for personal pages.”
Marek
Participanthow can i hit the limit while there is only one auto post for blogger there ?
It’s kind of hard to answer, because your issues contradict each other.
#1. Your API is outdated.
#2. Please see the answer in the FAQ – #1.10:
#3. You are using free API and hit it’s limit.
April 30, 2015 at 3:46 pm in reply to: Error posting to LinkedIn personal pages but not company pages #419281LauraVM
ParticipantThanks for your quick response, but I don’t understand. I followed the instructions, and it worked at first back in February. But now it doesn’t. I tried to delete the account in SNAP & set it up again. That didn’t work either.
Now I’m trying to set up SNAP for LinkedIn on another website I manage, and it won’t even authorize my company page this time!! The LinkedIn Developer App pages changed, too. It’s not showing me the oAuth User Token & Secret anymore, and asking for more info that it didn’t ask for before. I’m getting this error:
401
1430422775387
85NOP5GLES
0
[unauthorized]. The token used in the OAuth request is not valid. consumerKey: 78k251ccft4okeApril 30, 2015 at 3:41 pm in reply to: Error posting to LinkedIn personal pages but not company pages #419275Please use LinkedIn APi, not Nextscripts APi for personal pages.
Issue has been resolved by Facebook. We can confirm that it’s working.
Right now we are back to the original solution.
If you still have the problem, it means you are using outdated version of the plugin. Please update plugin to the latest version and re-authorize Facebook
Guillermo
ParticipantSeems like we are back guys! Thank you SNAP team for your patience and support!
Charles
ParticipantIt’s spreading guys 🙂
Tri
ParticipantAnd we’re back. Good luck everybody!
Marek
ParticipantReally i need help. how to fix this ?
Tri
ParticipantSame issue with our app this morning. Funny thing is the app was already using API 2.2 (not 1.0).
Anyhow, I updated SNAP first and reauth, but that didn’t help. Then I created a new app and that does use API v2.3, reauth but that still doesn’t fix it. Look like we’re waiting for Facebook to fix this on their end.Anthony
ParticipantThank you for the information. I now have answers I can give my bosses. I’m keeping an eye on this. I have faith that they’ll have it fixed soon.
[April 29, 2015]
[Facebook] Are you getting one of those errors?(#283) Requires extended permission: manage_pages
(#200) Requires extended permission
(#200) The user hasn’t authorized the application to perform this actionSOLUTION:Facebook moved EVERYBODY to the API 2.3 on April 30, 2015. If you got one of those errors you were on API 1.0. SNAP Plugin is compatible with API 2.3 ONLY starting from version 3.4.16. Please update your plugin to the latest version and re-authorize Facebook.
PLEASE DO NOT OPEN TICKETS ABOUT THAT.
UPDATE – [April 30, 2015]
It looks like Facebook screwed some accounts completely and even update/re-authorization doesn’t help.
We are looking for the solution.
You can see progress here and/or here
UPDATE 2 – [April 30, 2015]
It turned out that Facebook broke it’s API for about 80% of all accounts. We can only wait for them to fix it.
UPDATE 3 – [April 30, 2015]
Facebook officially admitted – it’s their fault. Facebook broke it’s API all by itself. There is nothing we can do until they fix it.
Here is the official BUG from Facebook: https://developers.facebook.com/bugs/380833342117530/- AuthorPosts
