I've been using the code here to handle Facebook logins:
https://developers.facebook.com/docs/facebook-login/web#example
https://developers.facebook.com/docs/plugins/like-button
I recently added the Like button but it appears that there is a separate flow for handling the login information that allows likes versus regular logins. Normally, when I log out, FB details (e.g., friends) can't be retrieved until another Facebook login is established. However, with the Like button, even if I logout and log back in or even log in with a different username, the Like button still works and is tied to the original FB user. To make that more clear, here's what happens:
Session 1 (FB user): FB like button is clicked --> FB login dialog pops up, info is entered, and like shows up on Facebook --> Log out
Session 2 (Other user): If the button still shows that the page is liked, clicking it again shows that the first user no longer likes the page on the actual Facebook page. Clicking it again to like the page again shows the first user liking the page again.
I'd like to tie the Like button login information to the regular SDK login. I'm reading that there is a lot of security around the Like and Share buttons so I'm wondering if that's even possible.
Related
What is the precise behavior that should be expected of the Follow Company button (https://developer.linkedin.com/plugins/follow-company) provided by LinkedIn?
If a user is already logged into LinkedIn, nothing appears to happen when the user clicks the FOLLOW button. Clicking the button WILL
cause them to follow that company, but the user must manually navigate to the company's LinkedIn page to confirm this.
If the user is NOT logged in to LinkedIn, clicking the FOLLOW button prompts a login in a popup window, but submitting credentials does NOT change the users FOLLOW status with the company, nor does it take the user to the company's LinkedIn page. Other than logging the user in, there is no effect.
Is this behavior what's to be expected of the LinkedIn FOLLOW button? Has anyone managed to have the button require login and then have it follow the company in one process?
I have one button and I want to share the content on Facebook without opening Facebook dialogue box.
Present code works like:
Click on a button;
It opens Facebook share dialogue;
And again click on share from dialogue;
I want something like this: click on a button and it would be shared on Facebook.
https://developers.facebook.com/docs/graph-api/reference/v2.2/user/feed#publish
You would need to authorize the user with publish_actions to do that. You need to go through the Login Review process with that permission and the message parameter must be 100% user generated according to the platform policy.
A lot of things to consider, i´d just stick to the popup.
Right now the "Like" button is not rendered if the Facebook page it links to has restrictions based upon age, country or content-type. The button only appears if the user is logged in to Facebook and his profile allows him to see the page.
The restrictions need to stay in place, but I want to display the like button along side the number of likes and have it prompt the user to login to Facebook instead of the button not showing at all.
I don't want to create hacks around the widget (if that's even possible) so is there a configuration or something to have the button show up even if the user is not logged in?
When a user which is not logged in to Facebook or Twitter, clicks the like/tweet button, a popup comes up asking the user to log in. This popup is not blocked by popup blockers of any kind. in IE for example, it opens up but anyway IE state a warning to the user. The bottom line is that all buttons probably use the same method.
I have a button that people click on it and it should open a similar screen, but it always gets blocked.
The button (in JS) works pretty much like FB like button. It checks if the user is logged in. If he does, then send the "like" to the servers. If he does not, then the login popup appears (and gets blocked).
So, it is a initiated by a user although not fully direct outcome, since we need to check if he logged in or not.
What is best method to do that?
The Popup Is activated by a click using the like, tweet button and they actually show only 1 popup. If you want, you can try by using only a single popup based on click for your website and you will definitely be able to understand this.
Facebook Connect has a recent bug that is causing the permissions pop-up window to not close and refresh the parent window as it is designed to do. Instead, after approval by the user it attempts to load the page directly in the pop-up window which is an awful user experience and really hurting our registrations. You can see the bug by registering for our site using Facebook Connect: http://alltrails.com
The URL of the page after the user connects that Facebook Connect is incorrectly loading in the permissions pop-up window is of the form:
http://alltrails.com/?installed=1&session={"session_key":"2.Gu0duOqdElNjXRac5wnetw__.3600.1283799600-1486832834","uid":1486832834,"expires":1283799600,"secret":"tKFaEgBTF9RJeuQZfYUSCw__","base_domain":"alltrails.com","sig":"a8dd9f75418b530ae6c3d935e14274c4"}
I'm hoping that someone much better at JavaScript than myself could suggest a simple code snippet that we could add to our homepage that would only be invoked if the page URL includes '?installed=1' and would do the following to allow the same user experience as Facebook Connect was intended to provide:
Close the permissions pop-up window
Load the appropriate page http://alltrails.com/register/facebook in the original parent window
I've tried to do this a bunch of different ways but haven't had any luck with getting it to work correctly. Thanks in advance for your help!
It's a (unconfirmed) bug.
http://bugs.developers.facebook.net/show_bug.cgi?id=12260
Hopefully it gets more votes so it gets fixed - vote people!
In the meantime, i am (attempting) to employ the following 'creative workaround':
Add logic to my Default.aspx page to detect that URL they are redirecting to in the popup.
Redirect to my page, FacebookInboundAuthorization.aspx, preserving querystring.
On load of that page, register some JavaScript to close the popup and manually fire the "onlogin" event handler for my button.
EDIT - Another possible solution
So i do something like this for the "Disconnect from Facebook" button, which has a similar bug which has been in FBC from day 1. If the user is already logged in, and you click the "Disconnect from Facebook" button, the "onlogin" handler is not fired.
So what i ended up doing is replacing the Facebook Disconnect button with my own regular anchor tag, mimicing the Facebook CSS. This way i can have full control over the click event (fire the function i want).
So, this principle could (theoretically) be applied to this current bug.
That is, after you do FB.Init on client-side:
Check FB auth status using FB.Connect.ifUserConnected
If user is connected, hide the regular FB:Login button, and show your "fake" FB Login button. Copy across the "onlogin" function from your regular FB:Login button to your fake button as the onclick event.
Your Fake FB Login button would be a regular anchor tag, with the same CSS applied to the regular FB Login buton.
So essentially, if the user is already connected, we don't really need FB's intervention for authentication, we can just do whatever we want (request perms, redirect, etc).
That should work.
Unfortunately i have higher priority things i need to work on, but it sounds like this is top priority for you.
So give that a go, hope it helps.