I'm trying to create a page that requires visitors to 'Like' a Facebook Page before showing all the content.
The page with the like button is hosted on herokuapp.com but the URL to like is a Facebook page (ie. the host URL and the 'Like' URL are different).
I've successfully included a like button and I have subscribed to the edge.create event, and everything was working fine (I could write to console.log or run custom javascript) when clicking on the Like button.
However in the course of testing I've clicked Like/Unlike so many times that my site has now been flagged as potential clickjacking and the Like button now changes to 'Confirm' and asks the user to go through the Confirm dialog process.
I understand that I just need to accumulate more 'white' Likes and this dialog will go away eventually, but in the meantime it's causing me problems.
Basically, when I go through the 'Confirm' process in Google Chrome or on my iPhone, the 'Confirm' link never changes to 'Liked', the number of likes doesn't change and the edge.create event doesn't fire.
Has anyone else encountered this behaviour? I've read just about every post on Stack Overflow relating to either the Confirm process and edge.create but no one seems to have had this particular problem. I'd really appreciate any suggestions :)
I was able to resolve this problem by moving my app to be hosted my own domain instead of heroku, even though I was liking the same page. Not an ideal solution for everyone but it worked for me. In future I will create dummy apps and pages to test this process out.
Related
I want to integrate facebook api to help in the registration process in my website. It was working fine before - the standard fb login button appears, the pop-up window to login to fb was working, some of the user data are obtained. However after several trials with me modifying the code as the feature isnt fully integrated yet in my site, whenever I press the login button what replaces the fb login page is "This webpage is not available." I already retracted the modifications I made to the point that it was back to the version wherein it was working before. I also created another app and replaced the app id and secret key, still it displays the same message. I do not know what is wrong. Please help.
Update:
I uploaded the project files to another hosting site and it works! Could it be that the previous domain is now blocked?
Please read the other posts, dude... we're all waiting for the FB to fix the issue...
I have successfully integrated Paypal Embedded Chained Adaptive Payment system.
I have been testing it in sandbox environment. On GOOGLE Chrome, when user initiates the payment procedure, a light box gets opened with a login button inside it, but once user clicks on that login button, user comes across with following message
"Please continue with your purchase in the secure browser we launched. If you don't see it, click on Go."
The reason for this is that Chrome blocks the paypal login pop-up window. End user would not be able to figure out that what happened. Most of end users would not be aware about that paypal login pop-up window being blocked. Can we do something here so that we can avoid that pop-up window and can perform whole operation inside the Iframe only ?
Is there any solution this problem ?
Will it get resolved automatically once we shall move to production/live environment?
Please help me out.. We are going live very soon!!
I have been playing around with this a lot today and I too encountered the same issue with the lightbox. HOWEVER after much fiddling and time I decided to just try expType="mini" and it worked flawlessly. I did find one site that managed to get chrome to display the lightbox method correctly, but it was only successful about half of the time. It seems chrome is very sensitive to popups and sometimes it can be fooled and sometimes not.
Anyway the solution I found that worked was to scrap expType=lightbox and just go with expType=mini - seems to work without any problems. In the back of my mind I'm a little concerned that future browser releases (in particular chrome) will have updated popup blocking code may soon block this too. I hope this remains working, but I don't have a great deal of confidence in it. Make sure you have the good old Express Checkout method as a backup.
Hope this helped.
I have a desktop app that was previously working. I call the FB app with: https://www.facebook.com/dialog/oauth?client_id=401292276603778&redirect_uri=https%3A%2F%2Fwww.facebook.com%2Fconnect%2Flogin_success.html&scope=manage_pages%2Cpublish_stream%2Cphoto_upload&response_type=token&display=popup
Recently, this has been getting stuck in IE at the permissions request page. No matter how many times I hit the "allow" button, it stays on the permissions request page. It doesn't get stuck in Firefox or Chrome. But since the desktop app uses an embedded IE browser, I'm now stuck. There's been no code changes on my end and I estimate the problem arose over the last week.
We're experiencing the same issue here.
It appears to be across any site - we've tried on Vimeo.com as well as our own and we can replicate the issue on each site.
The steps we're taking to see the issue are as follows:
Ensure you have a Facebook account that has never been used on the
site before
Ensure you are not logged into that Facebook account
Visit the website, click the Facebook login button
You’ll go to Facebook, log in
It’ll then show you a permissions screen with a button to Goto App
Clicking that button just results in an infinite loop where the page reloads and you see the same thing again
The issue can even be replicated on Facebook's own page on the developer site - http://developers.facebook.com/docs/reference/plugins/login/
This may end up being nothing more than a matter of preference, but I'd like to reach some sort of a consensus if at all possible.
I've got a page on which there a several different items that a user might want to share on Facebook. Were it still 2010, I would simply attach a "Share on Facebook" button to each of these items and have that button draft a corresponding wall post when clicked. But as we all know, Facebook has chosen to deprecate the share button in favor of the 'Like' button. Problem is (as far as I know) the Like button is specific to a page. This poses two problems:
I can't attach a different Like button to each of the different items a user might want to share.
Since the content on the page is not static, a user clicking the like button might be told that a certain number of people have already liked that item, despite the fact that the other likers in all likelihood (no pun intended) clicked the button for a completely different item. The fact that the URL remains the same causes trouble.
I recently bought something on Amazon, and was immediately taken to a page where I could Share my purchase on Facebook. Not Like. Share. I clicked the button, and it opened a modal window with a pre-drafted wall post. Does this mean that Amazon is using the deprecated share button?
Would using the Share button in 2012 be totally out of line?
Here you can find the code needed for implementing a custom Share button.
redirect user after facebook share and publish
I hope it helps you.
Came into the office today to do some more work on my nearly completed Facebook Connect website application.
And i have discovered for some reason, the "onlogin" event of the fb:login button FBML control is no longer getting fired!!?!
To anyone else that has a Facebook Connect FBML app (and using the JavaScript API for authentication), i would advise you test your application to make sure it's still working.
A friend of mine's app (which is live) has also stopped working as of today.
What's happening is you click on the "Connect to Facebook" button, it shows the FB login dialog, you log in.
Yes, they are being logged in to Facebook correctly (thankfully), but the "onlogin" callback event is not getting fired anymore, so the page just sits there (where before the "onlogin" event would redirect to the homepage, for example).
Of course if you refresh, you are logged into Facebook.
Seriously, WTF - what have those developers at Facebook done now?!?!.
Any ideas? Has anyone read any updates/threads on this issue?
UPDATE:
8 hours and still no fix in place. I've tried to do some workarounds (there is also an onclick event of the FBML Login Button), but it's all too early in the authentication cycle.
We need to be able to hook into a post-login callback to do things like redirects, permission popups, authentication logic, etc.
Nothing we can do without Facebook fixing this.
I just hope when i come in the office tomorrow this will be 'magically' fixed, much like this issue 'magically' appeared.
Well judging by the comments here i'm not alone. It's obvious at this point that Facebook have made a change somewhere, without telling us.
I just hope they rectify this issue ASAP as there is no workaround i can see for this.
UPDATE 2
Yep - (drum roll), its yet ANOTHER bug from that team of world-class developers at Facebook: (thanks Anon for finding link) http://bugs.developers.facebook.com/show_bug.cgi?id=11733
I love it how the comment from the FB guy Marc says "Only seems to be happening on old Facebook Javascript SDK", well, enable us to do server-side authentication with your Graph API (instead of just for retrieving user details/posting), and we wont have to use the old JavaScript API!
Fun and games.
FINAL UPDATE
Facebook have (seemingly) fixed this.
Let's hope it stays fixed.
Given the 'correct' answer to Anon (as he found the link).
Please confirm and vote on this bug... this should be fixed asap!!
http://bugs.developers.facebook.com/show_bug.cgi?id=11733
if in FB.getLoginStatus you are passing second parameter as true, pls make it to false.
I resolved callback issue using this trick.
Thx
This is a bug and they are about to fix it