LinkedIn Follow Button Requires External Login on Website - javascript

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?

Related

Redirect user to specific website based on location when user clicks on webform pop up link

We have a link on a website.
When user clicks on the link, it pop ups an online form.
Customer wants that if a user from outside the USA clicks on that link, user gets redirected to another website.
Is this doable?
Website is based on latest Drupal 8 Version just in case there is a module that does that.
You can use form use hook_form_ID_alter like this.
function hook_form_FORM_ID_alter(&$form, \Drupal\Core\Form\FormStateInterface $form_state, $form_id) {
// get the IP address of user and determine where they are coming from
// Follow this https://stackoverflow.com/questions/12553160/getting-visitors-country-from-their-ip
// Redirect user
// Follow this https://drupal.stackexchange.com/questions/146185/how-to-create-a-redirection-in-drupal-8
}

Facebook "Like" button versus Facebook login

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.

How to make sure that the user did shared site page on the Facebook wall

For example, the user presses the button "Share this page with Facebook". How can I verify that this record/post was created and exists on his Facebook wall?

Display Facebook "Like" button when user is not logged in

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?

Facebook authentication

I have an application which displays canvas page, even though the user clicks "Dont allow" button in a request dialog. Here is my issue:
Load the page http://174.123.24.242/fb_leagle/fbhome.aspx
Login my application through facebook login page of my application.
Click on "Dont Allow" button in a request permission dialog.
In issue #3, if he clicks "Dont Allow" button it will also display the canvas page, and when I click the "BACK BUTTON" of the browser the next dialog appears. Actually I need to skip the canvas page from displaying when user clicks "Don't Allow" button and redirects to the next dialog.
This is my login URL of my application: pls review it and guide me where i need to change it.
Blockquote
**https://www.facebook.com/login.php?api_key=************&skip_api_login=1&display=page&cancel_url=https%3A%2F%2Fapps.facebook.com%2Fleaglecases%2F%3Ferror_reason%3Duser_denied%26error%3Daccess_denied%26error_description%3DThe%2Buser%2Bdenied%2Byour%2Brequest.&next=http%3A%2F%2Fwww.facebook.com%2Fdialog%2Fpermissions.request%3F_path%3Dpermissions.request%26app_id%3D***************%26redirect_uri%3Dhttp%253A%252F%252Fapps.facebook.com%252Fleaglecases%252F%26display%3Dpage%26response_type%3Dcode%26canvas%3D1%26perms%3Dpublish_stream%252Cemail%26from_login%3D1&rcount=1**
pretty format of this url:
https://www.facebook.com/login.php?api_key=************
skip_api_login=1
display=page
cancel_url=https%3A%2F%2Fapps.facebook.com%2Fleaglecases%2F%3Ferror_reason%3Duser_denied%26error%3Daccess_denied%26error_description%3DThe%2Buser%2Bdenied%2Byour%2Brequest.
next=http%3A%2F%2Fwww.facebook.com%2Fdialog%2Fpermissions.request%3F_path%3Dpermissions.request%26app_id%3D***************%26redirect_uri%3Dhttp%253A%252F%252Fapps.facebook.com%252Fleaglecases%252F%26display%3Dpage%26response_type%3Dcode%26canvas%3D1%26perms%3Dpublish_stream%252Cemail%26from_login%3D1
rcount=1
According to the OAuth Dialog Documentation, the user will be redirected to the original app-page.
If the user clicks "Don't Allow", the browser will redirect to
http://www.example.com/response?error=access_denied&
error_description=The+user+denied+your+request.
I suggest you use the $_GET['error'] variable to recognize users that denied the request!
The different errors can be found here

Categories

Resources