I'm having a problem with a facebook like button.
The problem is as follows:
When the user clicks the like button, a post-on-the-wall dialog appears (called with edge.create) but in just half a second, the dialog disappears.
Another thing is when you usually click a fb like button, your like is instantly processed, no problems here, but in my page, when you click the like button, the dialog windows appears, after a moment disapperas, and the text on the like button changes to "Confirm",
and only after pressing "Confirm", the like is processed.
(I am using the javascript api)
The problem should be obvious, but again - why does the dialog window disappear, and why does the like have to be "confirmed" ?
I've been banging my head with this problem for a few days and I really can't take it anymore, so any help would be GREATLY appreciated.
Thank you.
The confirm button usually shows up when a new like button is getting many clicks in a short time period to help battle "like-jacking". This is not a coding error, rather a facebook controlled function.
Related
I'm using the facebook like box in a project. The issue there is that when I'm log out and click on the like button, it open a page asking me to log in, that's fine, but if I close that page and click again on the like button, that page it's not open again, the only way to solve the issue, it's refreshing the page.
Here is a video to show the issue http://screencast.com/t/z8fNAGDqYuS, every single time that the cursor is on the like button I'm making click on it, and it's not working.
Does anyone know how to solve that issue?
Thanks in advance
I'm trying to know when an user clicks on the "like" button.
Everything I can find leads me to the "FB.Event.subscribe('edge.create', ...)" thing, but it doesn't seem to work on page tabs...
Does anyone know a way to capture this event on tabs ?
Thanks a lot for your help.
I make a mobile web with a like button to simulate a like gate-way.
When user click on it, it triggered edge_create event, the like button turn grey, but then it revert immediately and go to the fan page.
But if the user press on the like button long enough, the like action is triggered correctly.
I cannot figure out what is the reason and how to fix it...any one has the same issue?
I am using Addthis plugin. I have an "F" icon on the page. I want it to work as recommend functionality.
is there anyway to do following
if somebody click on F, it should work as recommend is clicked, and on move over this F, it should just show the Count of recommend
we do not want to show standard recommend box with count
Secondly question, when i click on any like button it also show another Share Popup, but even even if i cancel this popup, still my timeline show i have recommended that particular page.. then what is use of that popup.
You can use the Facebook Dialog JavaScript to show a Share dialog for a custom button. Or use the Send Dialog button to create a private share dialog.
The "Comment Box" on the Like Button is optional, it's not required. If you enter a comment, it adds it to the Like post that appears on your timeline. But you can still like a page without entering a comment. A Like with a comment appears more prominent on the user's timeline.
I have an activity with a mayStop() method. I am having two issues with it that pertain to a hyperlink on the page.
The first issue is that if I hit refresh or the window's X I get a dialog box that wraps my mayStop() text with "Are you sure you want to navigate away from this page?" and "Press OK to continue, or Cancel to stay on the current page." That is fine.
When I hit the hyperlink, I only see my mayStop() text without the wrapping text. Why is that?
The second issue is that if I hit Cancel in response to the hyperlink click, hitting the link again results in not getting the mayStop() challenge at all. It is as if I am not hitting the hyperlink.
Has anyone run into these issues?
Any thoughts?
Thanks,
Doug
The difference in "behavior" is that the first dialog box is the one from the browser when you try to prevent the user from navigating away, while the other is PlaceController calling Window.confirm(). Each browser uses a different dialog box for the first case, so there's no way to mimic it for everyone, and it's probably not a good thing either (navigating away from the app vs. navigating within the app).
As for your second issue, the events are generated by the browser "history" changing; if you prevent navigating away (from the Place), the URL stays the same (there's noway to know what to do to "rollback" the change: History.back(), History.next(), History.newItem() but then you destroy the existing "next" history ?), so when you click again on the link, you don't make the URL change, and no event is fired.
It's expected that you use PlaceController.goTo to navigate when you use places, not Hyperlink or History.