in earlier version of graph api they had manage_pages hook now they have depreciated that.
as far as the documentation says, we have to use 4 different request for using those permission now.
pages_manage_metadata
pages_manage_posts
pages_read_engagement
pages_read_user_content
is there any way we can use manage_pages ?? as these above permission requires lot of hard work like signing contract with facbook etc
any help will be great.
manage_pages was great feature
According to a blog post by facebook mentioned in docs:
Developers that already have access to manage_pages and publish_pages will be automatically migrated to the relevant, new permissions by June 1, 2020, and access will remain undisrupted.
Developers with no existing access to manage_pages or publish_pages should actively monitor their app dashboard for the new permissions as they begin rolling out today. By June 1, 2020, all developers will see the new permissions and are encouraged to apply. After this date, applications for manage_pages and publish_pages will be unavailable and no longer reviewed.
Relevant part is they have mentioned that developers that already have access to manage_pages will be automatically migrated, so there is no way you can use manage_pages after June 1, 2020.
Related
I'm trying to make an app that will allow blog posts from my website to be published to a Facebook page which I am the admin of.
Obviously I need the publish_pages and manage_pages permission to do this and I need to provide a screencast showing how these permissions will be used.
From my understanding, I can still publish a post from my website to my Facebook page while the app is in development mode as long as I am the admin of the page (which I am) but the posts won't be visible to the public.
So I complete the authentication process here (see below).
Finally I add my blog post. However, I then get the following as an error message
"(#200) The permission(s) publish_actions are not available. It has been deprecated. If you want to provide a way for your app users to share content to Facebook, we encourage you to use our Sharing products instead."
Would this be an issue with the system I am using, making a depreciated API call?
Deprecation:
The publish_actions permission will be deprecated. This permission granted apps access to publish posts to Facebook as the logged in user. Apps created from today onwards will not have access to this permission. Apps created before today that have been previously approved to request publish_actions can continue to do so until August 1, 2018. No further apps will be approved to use publish_actions via app review. Developers currently utilizing publish_actions are encouraged to switch to Facebook's Share dialogs for web, iOS and Android.
From now on you can only publish to your own facebook profile not facebook page. For more information you can visit their official documentation
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'm quite confused about Facebook's new publish_pages permission.
My Facebook app allows our CMS users to post to their Facebook pages via our CMS, posing as the page.
We have been granted (via the login review process) the manage_pages and publish_actions permissions.
The API change log states this:
publish_pages Permission - This new permission is required to publish as a Page. Previously publish_actions was required. People who granted manage_pages and publish_actions before v2.3 have automatically been granted publish_pages. If anyone logs in via v2.3, you'll need to request publish_pages explicitly in addition to manage_pages.
We have not been granted the publish_pages permission automatically.
The blog post here states:
For Page developers, we've added the ability to deliver more content on a Page via real-time updates (RTUs). A new Login permission, publish_pages , is now required for apps to publish on behalf of Pages; previously, this required publish_actions.
So it sounds to me like if we upgrade to use API 2.3, our service will no longer work, because we haven't been granted publish_pages.
The documentation states this:
A user access token with publish_actions permission can be used to publish new posts on behalf of that person. Posts will appear in the voice of the user.
A page access token with publish_pages permission can be used to publish new posts on behalf of that page. Posts will appear in the voice of the page.
We do want to post in the voice of the page, as we do currently.
Therefore I opened a new login review request and summarised all of the above, quoting their changelog. Facebook's response was this:
You don't need the publish_pages permission because you already have the publish_actions and manage_pages permissions granted. Publish_pages is a new feature that allows an app to publish to a managed Facebook fan page, but your previously granted permissions contain this functionality already.
Is it just me, or does that response conflict with everything else they've written?
So my question is simply, do we need this new permission going forward or not, and have they wrongly not automatically granted it to us?
Well apparently Facebook's supports response is in some manner wrong.
If you want to post on Page on behalf of the user manage_pages and publish_actions publish permissions are passable for post action.
If you want to post on behalf of the page you also need publish_pages permission, without this all v2.3 api calls will return OAuth Error. There might be other privileges for managing your pages under this permission i don't know
I created facebook app for my website & To enriches the user's experience i need extended permissions from facebook for my app ( which includes read_stream with some other permission ) , i have submitted the app for reviews with valid description but submission were not approved and i could not find any valid reason for that.
I noticed this description in read_stream -- Android and iOS apps will not be approved for this permission. In addition, Web, Desktop, in-car and TV apps will not be granted this permission. , can you please explain meaning of this ?
Here is my reference site - https://hootsuite.com/ , they are using read_stream as well.
Hootsuite is using a v1.0 App created before v2.0 was introduced. It will stop working for them after April 2015, when they have to go through the review process too. You will not get read_stream approved for your website, as you can read in the quote you posted.
Meaning, you can only use read_stream in an App created before end of April 2014, and only until end of April 2015. Not worth using it anymore imho.
It's all in the docs:
https://developers.facebook.com/docs/facebook-login/permissions/v2.2#reference-read_stream
This permission is granted to apps building a Facebook-branded client on platforms where Facebook is not already available. For example, Android and iOS apps will not be approved for this permission. In addition, Web, Desktop, in-car and TV apps will not be granted this permission.
So, I strongly doubt that you'll receive this permission during app review.
Now someone can use "user_posts" permission - This new permission allows an app to access the posts on a person's Timeline. This includes the someone's own posts, posts they are tagged in and posts other people make on their Timeline.
This is a useful alternative to News Feeds.
Previously, this content was accessible with the read_stream permission. The user_posts permission is automatically granted to anyone who previously had read_stream permission.
Facebook Platform Changelog
I have a app with some permissions that only exist on API V1.0 (I'm working on migrating them to V2.2),
but in the meantime I need a new permission "publish_actions". If I send a review to Facebook I can still use the API V1.0 permissions or I can't? how can keep my permissions "read_stream" of API V1.0 and add a new one?
Best,
You send in specific permissions, so you can just send in publish_actions without read_stream and it should be no problem. Just keep in mind that you will lose access to read_stream completely after April 2015. I assume you know that it will only get approved for platforms without a Facebook client.