-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Facebook Graph now v3.0 - tokens no longer working #337
Comments
Oh yes, I'm not alone... welcome to issue #330 . |
Possible fix, tested and currently working: go to and grab the token it generates from here. |
I generated new access token using my App id and app secret but when i put it into the social-feed.js it still dont show facebook page feed, in example (https://pavelk2.github.io/social-feed-example/) facebook is working, please help me too so i can make it work too. |
@mutiullah7, don't bother with that. Most probably new FB API won't work with this plugin. As an alternative I suggest you to try free option at juicer.io. |
Hi @vushe i created new access token using app id and app secret its working again for me |
Great to know, @mutiullah7. Thanks for feedback! |
thank you @mutiullah7 and @vushe your discussions has really helped me fix the plugin. As said in other posts, update your socialfeed.js to v2.12
After you've changed the above, go to this link and generate your new access code -> https://developers.facebook.com/tools/explorer/145634995501895/?method=GET&path=me%2Ffeed&version=v3.0 Add that into your js file and BOOM - fixed. Thanks again!! |
I believe the access codes which are generated by that link are time restricted. |
Facebook has updated the graph API to v3.0, and now tokens are no longer working. However, it appears that tokens created before v2.12 are still functioning.
I switched the version in socialfeed.js, but it did not work.
I also scanned Facebook's Broken Changelog and came up empty-handed.
Any help you can offer would be much appreciated.
Thanks for the great plugin!
The text was updated successfully, but these errors were encountered: