FB like button reverted after clicking on it

I have the same problem. The button works on old nodes, but on the new ones it is reverting.

Like button in node teasers and in full node only works if you have url mode set to unaliased in the main settings page (admin/settings/fb/social/settings).

Same behavior, but I'm on 7.x-2.x-dev. Aliased or unaliased URL, doesn't matter. Flickers for less than a half second and then reverts to zero likes.

Same bug here.

I had to disable the module, uninstall the module and then reenable it and reconfigure it to have the Like button stop flashing and work correctly.

But it worked only on a few nodes, other nodes are still flashing back!

Using 6.x-1.0-beta 8. I downgraded to 6.x-1.0-beta 6 and I have the same problems. Some nodes are working while others are not.

It's not always the newer nodes that do not work.

Also, when using only the iframe content in a window, I see the flashing:

https://www.facebook.com/plugins/like.php?action=like&api_key=...................

So Facebook is not reliable.

I have the same issue, but only when I add the "Like" button to a View...

The problem seems to exist only when I'm not logged in to facebook on firefox (6) on Ubuntu linux. In Chrome it worked repeatedly after Iogged back in and out, same in IE9 and firefox (6) on windows 7.

edit: it also doens't work when I'm logged in on firefox 6/ubuntu. other browsers I tested do work
- IE 9
- Chromium/ubuntu
- Firefox 6 Windows

edit2:
Solved?
I enabled 3rd party cookies, that did it for me (or so it seems).

I confirm that buttons work on Mac with Chrome and now Firefox 6. Last time I check with Firefox 6, the buttons did not work.

Looks like this is a Facebook bug! I am not sure if it's related to the way this module create the buttons.

I have been trying to get my head around this for a couple of weeks. For those of you that have some nodes working, but not others, can I check if the input format was set at full html or filtered. It might not have any bearing on the solution, but I would like to see if this has been the case for others.

I wasn't getting any nodes working, but after changing the input format default to full html it has worked on new nodes. However it has not made any difference on nodes that started out as filtered and since changed to full.

I'm getting the same flashing button problem. My nodes are using Filtered HTML input. The like button is applied via Display Suite to the node teaser.

I had this problem too. It started working again, after I changed my facebook application's site url from domain.com/ to http://domain.com/

@perohu: You are right. I am running a website which have a lot of domains pointing to the same document root. So a single website with various domains.

Facebook will accept a single domain. So all domains except the one defined at Facebook did not work.

Now I am redirecting all domains to the main one.

We may be able to close this issue of other can confirm that fixing the url on the Facebook application page fixes this.

Same issue here, but it wasn't random. I installed the Open Graph Meta Tags module, and new nodes for which the tags were enabled had the broken like button. Nodes created before Open Graph were installed still worked properly. After disabling the open graph module, uninstalling it, then checking the affected urls in linter, the like counts came back.

On one site I resolved in part the flickering issue (button flashed on and off quickly) by:

1. …first going to my Facebook and disconnect.
2. Going back to the site where I installed this module and clicking the I like button.
3. A window will pop up asking for credentials and the like button will work.

But then, again, I might not be able to use the I like button a lot, it will start to flash again and I would need to go back to Facebook to disconnect again.

Looks like Facebook have difficulty reading cookies to see if I am still connected. This problem also comes and go with time.

On another site, I am using an older version (6x-1.0-beta6) of this module and I don't see any problem.

I had this problem too and found it was a bad url in data-href. I'd put the relative url, when I changed it to the fully qualified url, it worked again.