To use my website, it is essential user need to give pages_show_list permission.
Seems after Facebook login, in development mode Facebook do not ask about granting permission, why?
The only way I worked it out is with Facebook Graph Explorer. It will force to show permission popup, and set permission.
But what about real time users? What if accidentally they do not grant permission, is it a way - not with Graph Explorer - from Facebook to give permission later?
https://developers.facebook.com/docs/reference/javascript/FB.login/
Play around witz the auth_type for that. You can also check for authorized permissions with the /me/permissions endpoint: https://developers.facebook.com/docs/graph-api/reference/user/permissions/
Related
I am attempting to get events from a specific page, through a person who is administrator of the site and the host of the events. This will not work unless i make the administrator a tester on my Facebook App. Anyone who knows which permission i am missing?
I have the following permissions already:
business_management
manage_pages
public_profile
publish_pages
user_friends
EDIT
Facebook API Explorer
Facebook API Explorer
Access Token Info
https://developers.facebook.com/docs/graph-api/reference/page/events:
This is a restricted edge. You cannot request access at this time.
Facebook has restricted this to specific partners; as a normal 3rd-party app developer you can not get page events at this time.
I have an app that programmatically make post on a configured Facebook Page.
My app obviously have both the manage_pages and publish_pages permissions approved and I'm using pages access token
Everything work well since now, but recently when I POST on page feed
https://graph.facebook.com/v3.1/234002440799692/feed
I get this error:
{"error": {
"message":"(#200) Requires either publish_to_groups permission and app being installed in the group, or manage_pages and publish_pages as an admin with sufficient administrative permission",
"type":"OAuthException",
"code":200,
"fbtrace_id":"HEVcI\/Tq3fW"
}}
I know that Facebook has deprecated publish_actions scope, so that it's not possible anymore to post programmatically on the personal feed, but I can't find out why the post on a page return this kind of error.
Some further infos:
posting with a developer account actually work
the user by which the page access token is obtained, created the page on Facebook (so I think it's an admin for the page)
i recently migrated from graph_api v2.12 to v.3.1
Any suggestion will be appreciated
Thanks
I figured it out what the problem with some pages is.
It seem that now, if the user grant the manage_pages and publish_pages permission, that will be valid only for already existing pages!
New pages haven't the permission granted by default.
The only way I can fix the problem was to remove my app from the user profile (Facebook Settings > Business Integrations > Select the app > Remove) and then prompt the user again with the Facebook OAuth permission dialog.
I don't know if there is a way to force the app removal programmatically, but I can't find out.
You can use the following URL:
https://graph.facebook.com/v7.0/234002440799692/feed?&access_token={access_token}
I'm using v2.5 of the Facebook Graph API.
What's the difference between manage_pages and pages_show_list permissions?
From the docs it seems that you need manage_pages to get a page access token. But I tried and I was able to get it with just the pages_show_list permission.
Is this a bug or am I missing something?
The docs are vague und not complete on this subject. Facebook says they grant pages_show_list to all apps (I can't confirm this, see this question), while manage_pages requires review by Facebook.
One import difference is the way the app is presented to the user. If you request manage_pages, the user will be told that your app wants to manage his/her pages before the user approves.
Besides that, the only difference I found in the docs is the fact that manage_pages combined with publish_pagesallows apps to, well, publish pages.
pages_show_list simply allows you to receive a list of the pages that the requesting user is an admin of.
I need user_posts permission on my web http://www.slevnime.cz/ and facebook every time deny this review with this message:
user_posts - Web - We could not reproduce the requested permission. Please
submit detailed, step-by-step English instructions in the "Add Notes"
section of the permission, and make sure to provide the relevant
version of your app. See here for additional information on login
permission requirements.
When people logging on my app, i ask for this permissions: email, publish_actions, user_friends and user_posts. Why facebook send me this message? Detailet step-by-step is writed fine.
Thanks for help.
Well, ask Facebook says, you should outline why and for what you need the user_posts permission. It should also be visible to them where in your application this is used.
If they can't see this, they will not grant you the permission.
My goal is to have my app be able to read my users stream using the extended permission "read_stream" , however when requesting that permission the dialog doesn't show me having requesting that permission.
I have no trouble requesting the email, or publish_actions permissions, but read_stream is a no go as well as other various extended permissions. Here is an example of what I am using for the facebook login:
https://www.facebook.com/dialog/oauth?scope=publish_actions%2Cread_stream&redirect_uri=http%3A%2F%2Fwww.MYDOMAIN.com%2Fsocialregistration%2Ffacebook%2Fconnect%2F&display=popup&client_id=MYAPPID
Is there another permission I need to request when requesting read_stream ? Is there something I need to change in my facebook app settings specifically for the scope permission request? My goal is to be able to get permission for "read_stream".
Thank you for any input!
The method I describe does work! The issue was that there is a second facebook prompt for the extended permissions that occurs AFTER the initial prompt for permissions.
What is confusing is that facebook shows permissions for email and publish_actions on the first facebook dialog box instead of in a consistant manner for all the extended permissions....but that's facebook's choice!
So hopefully this helps anybody else that was confused like me!