You mean this:” Invalid Scopes: read_stream, user_groups. This message is only shown to developers. Users of your app will ignore these permissions if present. Please read the documentation for valid permissions at: https://developers.facebook.com/docs/facebook-login/permissions”
Yeah I’had the same problem… hope this fix early
@melonos and @redwolf83 : can you please provide details about what error you are getting and steps to reproduce it?
The error is written above in the post of redwolf83
This is an error on the facebook developer site.
Reproduce it by trying to create the FB DeveloperApp
The error on “Add link to faebook” is that it cant be authorized
It is simply that Facebook changed its requirements for apps. Some permissions are not longer allowed.
Maybe its only to new users, because somewhere i’ve seen something like “you didnt request read_stream in the last 30 days, so you are not allowed to do this”
Maybe you should ask FB…
I just setup plugin for another FB user.
Use https://wordpress.org/plugins/add-link-to-facebook/other_notes/ for manual.
After “Press Save Changes” press in plugin-settings page “Authorize” and get this face-book error
Hello tanaylakhani,
I don’t think some permission is no more allowed because on another site that I own, the “Add Link to Facebook” plugin works perfectly.
I also asked review for the permissions “publish_action , user_groups , manage_pages and read_stream” following the “Setup guide” at page https://wordpress.org/plugins/add-link-to-facebook/other_notes/
but the reply of FB is this:”
Notes from our review team
General
Hi,
You do not need to request these permissions because your blog or CMS is integrated with an app that you admin. As an App admin, you can already access these permissions and post to your timeline or a page you admin. You can provide access to additional users by adding them as developers of your App.
—
The following items were not reviewed due to general issues with your app:
publish_actions
manage_pages
read_stream
“
Hope this helps.
So it seems that this is a problem only to new users
I think some FB API changed, I’ve tried to use also older version of “Add link to Facbook” (versions till 2.0) and tried the dev version too but always have the same error.
here’s how to overcome the public_actions review issue. have a look to the third answer:
http://stackoverflow.com/questions/27542929/publish-action-review-failed
Hm, I have tried the Plugin “Facebook auto publish” and that seemed to be enough to overcome the public_actions issue as described in the link you metioned.
But I still have to go through the full review process for the permissions publish_actions, user_groups, manage_pages and read_stream
Ok, the app review has been completed by Facebook. This is the answer:
“You do not need to request these permissions because your blog or CMS is integrated with an app that you admin. As an App admin, you can already access these permissions and post to your timeline or a page you admin. You can provide access to additional users by adding them as developers of your App.”
“The following items were not reviewed due to general issues with your app:
user_groups
publish_actions
manage_pages
read_stream”
And still I can not authorize Add Link To Facebook…
user_groups is no more available, hence creates an issue. We have modified the use and configuration. Let us know if the issue still persists.
same error as before while trying to authorize:
” Invalid Scopes: read_stream, user_groups. This message is only shown to developers. Users of your app will ignore these permissions if present. Please read the documentation for valid permissions at: https://developers.facebook.com/docs/facebook-login/permissions”
following because have the same problem …
Invalid Scopes: read_stream. This message is only shown to developers. Users of your app will ignore these permissions if present. Please read the documentation for valid permissions at: https://developers.facebook.com/docs/facebook-login/permissions
Just on one site. On another one (installed months ago, everything works fine).
The problem seems to be to authorize the plugin.
Once authorized it seems to be working (not really tested because I cannot authorize because of this damn error)
