Facebook API 2.3 的新 publish_pages 权限——我需要它吗？

Question

我对 Facebook 的新publish_pages 权限感到很困惑。

我的 Facebook 应用程序允许我们的 CMS 用户通过我们的 CMS 冒充页面发布到他们的 Facebook 页面。我们已被授予(通过登录审核流程)ma​​nage_pages 和publish_actions 权限。

API change log声明如下:

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.

我们没有自动获得 publish_pages 权限。

blog post这里说:

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.

所以在我看来，如果我们升级到使用 API 2.3，我们的服务将不再有效，因为我们没有被授予 publish_pages。

documentation声明如下:

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.

我们确实想在页面的语音中发帖，就像我们目前所做的那样。

因此我打开了一个新的登录审核请求并总结了以上所有内容，引用了他们的变更日志。 Facebook 的回应是这样的:

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.

这只是我的 react ，还是该 react 与他们写的所有其他内容冲突？

所以我的问题很简单，我们以后是否需要这个新权限，他们是否错误地没有自动授予我们？

Answer 1

显然 Facebook 的支持响应在某种程度上是错误的。

如果您想代表用户在 Page 上发帖，manage_pages 和 publish_actions 发布权限可用于发布操作。

如果您想代表页面发帖，您还需要 publish_pages 权限，否则所有 v2.3 api 调用都将返回 OAuth 错误。我不知道在此权限下可能还有其他权限来管理您的页面