Facebook 'Send me email' Permission - facebook

I have question regarding facebook permissions.
I'm looking to let my website users 'Login with Facebook'. I've created an app however I want the user to explicitly agree to letting my app send them emails (see image below)
I've checked the facebook developers pages (https://developers.facebook.com/docs/authentication/permissions/) and I can't seem to find a reference to the 'Send me email' permission that used to be available.
I can see it in the REST API documentation which has been deprecated but can't find it in the current documentation.
Any help on which permission to use would be much appreciated.
Thanks!

If you're setting up the permissions dialog via the Enhanced Auth Dialog (located in your app settings > Auth Dialog), simply use the 'email' permission as noted in the Facebook documentation when configuring the User and Friends Permissions section.
If you are using the sdk to prompt a permissions dialog, just add 'email' to the comma separated list.

Related

Did Facebook Connect add Email Permission as an extended permission?

Last I saw that 'email' permission in the authentication process was part of the initial dialog (along with basic information) for all apps. However, today I noticed that for my app it shows as an additional step (like extended permissions) after the user has accepted the initial authentication. See the screenshot:
I still see other sites/apps with old-style authentication (email in the first step). I wonder if I am doing something wrong with the permissions or app settings that is causing it? This is how my LoginUrl looks like
https://www.facebook.com/dialog/oauth?client_id=[app_id]&redirect_uri=[redirect_uri]&state=[state_code]&scope=email&display=popup
In the App settings on Facebook in the 'Auth Dialog' > 'Authenticated Referrals' > 'User & Friend Permissions' I have added 'email' and 'publish_actions' permissions.

Submiting Open Graph Read action

Facebook keeps rejecting my read action each time I submit it.
Please note that my open graph application functionality includes the deletion of an article as that is required by facebook.
you can visit my website at www.heyngine.com
Please advice
If you are using the Read action on your website, you must use the build-in read action (news.reads) and not create your own action for the same thing. Facebook will reject your action if its a duplicate of a build-in action.
Secondly, when you login to Facebook via your site, it doesn't ask for the publish_action permission. This is required to publish actions to Facebook. Without this, your read action will not get published to the user's profile. Also, why are the 'Social On/Off' and 'Delete' buttons visible when I'm not logged into your website via Facebook?
Facebook Documentation / Policy says the user must have a separate 'logged in' experience to logged out users. I.e. Facebook Users should only see 'Social On/Off' and 'Delete' once they have connected to your site via Facebook, not before as you do currently.

Automatically activate users' timeline on login

I am using the JavaScript SDK to login in the user on my website via Facebook, requiring the publish_actions permission. If I am getting it right, Open Graph stories published by using publish_actions are only visible for users who have their timeline enabled.
Is it possible to automatically activate the users' timeline after he logged in to my application and gave me the publish_actions permissions. I've seen authentication dialogs around the web where applications request the publish_actions permission and after granting the permission and logging in, the user automatically has the new timeline enabled.
I already searched a lot, but unfortunately I could not find anything in the developer documentation about how to do that.
How do I accomplish this?
If you request the publish_actions permission from the user and you have the action approved by Facebook, the message you talk about will appear in the login popup. Facebook automatically adds this message in as the features are only available with the new timeline profile. There isn't a setting you need to configure to add this message in.
What you describe is the intent of modifying user settings, and you can't do that.

Facebook email Permission, OAuth2, doesnt work?

since the new Auth Dialog from Facebook (for my App & homepage), I cannot get the dialog to show that my homepage/app needs the users email when connection to my homepage/app.
In the Auth-section of my app I've added "email" to the User & Friend Permissions. Also I've added it to the referal when someone clicks the "Login with facebook"-button.
When someone clicks the Facebook-button, he/she redirects to a page which has the PHP-code with Facebook SDK PHP (latest). Here's how I generate the send-to-url for the dialog:
$login_url = $facebook->getLoginUrl(array('req_perms' => 'email,publish_stream'));
header("Location: ".$login_url);
But when the Dialog pops up, the only permission request it does is "basic information". I need to request the Email. Am I stupid or is it a bug somehow? I've also recreated the App.
There in no req_perms parameter anymore, it's called scope in OAuth2.
Read documentation for getLoginUrl to see correct parameters.
in new dialog there are 2 kind of permissions normal permissions & extended permissions
you should install app with normal permissions at first then page will redirect automatically
for extended permissions

facebook fb.login two popups

I am having a problem with facebook authentication in facebook Page Tab. I am usin JavaScript SDK FB.login method. I need theese scope: 'email,publish_stream'} permissions. And then I am launching my authentication function I am getting two popups one which asks to login and gives email permition and other requires to allow to post on whall. My question is how to login with only one permission asking?
I found the answer to my question!
Go to https://developers.facebook.com/apps
Click on your app.
Click edit app
Click Advanced
Check Enhanced Auth Dialog: Disabled
Thats it. You have one authentication popup.
Take a look at this page http://developers.facebook.com/docs/reference/api/permissions/
Here they specify two types of permissions. Basic permissions and extended permissions. publish_stream falls in the second category and that is why you are getting two pages.
This is a new thing they have made to make sure users understand what they are giving access to.
"You can ask for the following extended permissions in the scope parameter of the Auth Dialog.
If you are using the Enhanced Auth Dialog, these permissions are revocable, and are presented on the second page of the Dialog."
This is because of the Enhanced Auth Dialog.