-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 SOCIAL_AUTH_FACEBOOK_SCOPE not working as expected #294
Comments
What are you trying to modify? Could you show me the API endpoints you are using? |
I am trying to post to a page. The endpoint is: I am basing this off of this documentation: https://developers.facebook.com/docs/graph-api/reference/v2.0/page/feed#pubfields No matter what I seem to do I still get a |
Are you trying to post in behalf of the user or the page? |
@omab is SOCIAL_AUTH_SCOPE more preferred than FACEBOOK_EXTENDED_PERMISSIONS and whatnot? because it seems like the social_auth tutorial did not even talk about SOCIAL_AUTH_SCOPE. If this is the case, how do you request information from SOCIAL_AUTH_SCOPE (like email or something) in the view function? |
In order to defined scopes, backend-related settings should be used, like |
@omab sorry, I actually meant SOCIAL_AUTH_FACEBOOK_SCOPE. Where can I see the things I can call for SOCIAL_AUTH_FACEBOOK_SCOPE? like email or user likes or photos? because I think the syntax for facebook scope is different from facebook_extended permissions? |
@tleewu, the docs about Facebook Scopes can be found here https://developers.facebook.com/docs/facebook-login/permissions/v2.0, there's a lot to dig in there and all depends on what you need for your project. |
This do the expected result for me. Hope it helps... SOCIAL_AUTH_FACEBOOK_PROFILE_EXTRA_PARAMS = { |
I have
In my settings file, but Facebook always returns
{"error":{"message":"(#200) The user hasn't authorized the application to perform this action","type":"OAuthException","code":200}}
with a status code of 403 when I try to modify a page.The text was updated successfully, but these errors were encountered: