I'm adding a Like button to a website and currently making a few tests. At first, everything was working fine, until the Confirm link started to show up whenever I clicked the Like button. I searched this and found out it is a spam control. So I understand the button showing up, since I am liking and unliking the site many times, for test purposes, and I'm OK with that.
The problem is that, even when I click Confirm and click Like again in the popup, the Like is ignored. The counter does not show any likes and the action is not posted to the Facebook wall.
The Facebook debugger does not show anything wrong with the url either.
Here's how to reproduce:
1. Access http://sjc.prima.net.br:8777/fb_test/like_test.htm
2. Click Like button
3. Click Confirm
4. Click Like again, in the popup
See that the Like is ignored.
Any help, please?!?
Related
I'm working on a site for a client. The site is built in Joomla and is using a Facebook like button on each page. When a user clicks a like button it unclicks itself after a second or two.
I've seen several similar problems here but none have provided enough insight to help me figure out what to do to fix this problem.
I ran the page through the Facebook debugger:
https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.theartoflove.net%2Findex.php%2F9-blog%2Fmen%2F27-go-ahead-and-ask-her-out
but I don't have a clue how to figure out what that result is telling me. The URL I used as a test in the debugger is:
http://www.theartoflove.net/index.php/9-blog/men/27-go-ahead-and-ask-her-out
Anyone know what I need to do to fix this problem? It seems to happen regardless of what like box I put on the site (I've tried three different ones so far).
My sincere thanks for any help!
When I clicked the like button, a small 'CONFIRM' link appeared under the "Like" widget, i had to click the 'CONFIRM' link (which brought up a dialog box asking me to confirm that I liked the page) in order to get the "Like" to stick.
See image
Facebook sometimes makes the arbitrary determination that your page is 'spammy' and adds extra precautions like 'CONFIRM'. That may be part of what is going on.
The code is reentrant and the developer is flipping the bit instead of verifying the current state with a conditional before setting the value. (This is a common coding mistake. Too common.)
After searching the internet and doing my own research on this subject I still can not find the answer to my problem, so here it is.
When I click the like button (to like my website http://openarchitecture.cz) then the like count is not being increased.
Debugging the FB javascript code on client-side (in Chrome) and examining the ajax response
send back from FB servers after the click on "Like" button, revealed that FB is instructing the Like button to be "disconnected", resulting in the behaviour described below.
The term "disconnected" is a strict FB term (in a sense of a javascript code), it means that on client-side there will be used a "plugin" that will perform certain operations leading to "inactivity" of like button. Technically, when the plugin "disconnect" is beeing recognized as part of the ajax response, there is an array of predefind actions (functions) that will be followed and called sequentially.
Now for the reproducibility of the problem.
Go to http://developers.facebook.com/docs/reference/plugins/like and fill the "URL to Like" field with http://openarchitecture.cz
url.
Click "Get code", then click "Ok" on the pop-up and finally click "Like" button on the right.
The like count should increase. Instead a pop-up shows up for (aprox.) 1 sec.
then the popup disappears. Now I am in the same state as before I click the
like button, i.e. like count is not increased.
I have found similar questions here on SO, but none of them seems to finally
resolve the issue.
The related questions here on SO are:
1. http://facebook.stackoverflow.com/questions/5195183/facebook-like-button-flashing-on-then-off/12958474#12958474
2. Facebook Like button does not work on one website?
One of the suggestions was that this migth actually be a FB bug. I found a (very recently created) bug, reported in FB bug tracking system. The bug is located here:
http://developers.facebook.com/bugs/268340209965207?browse=search_512b8e0bed9724580954683
The bug has however "Low" priority an so far it does not seem to be resolved (it might even be returned as not a FB issue, I am not sure if this possibility is still open).
So for all interested in this.
Is this a real FB bug ?
How have you dealt with this ?
Could it be that my site is for some reason on FB spam/black/"whatever nasty" list ?
Well. This will end up like the other posts, i.e. no lesson learned here.
[The term "page" used later in this post represents the http://openarchitecture.cz page]
I just tried today to like the page again via the FB generated like button (on http://developers.facebook.com/docs/reference/plugins/like/ ) and the result is now ok. So the like count gets increased after clicking the like button.
The difference that I observed when checking the request exchange to FB servers is that this time the communication has been done (by default. i.e. using the XFBML version of the like button) over iframe, not direct ajax call (as was in the past for XFBML).
I dont know what was the cause (I tried the pure iframe version of like button before) but the response going back as a result of the mentioned iframe request is now correct, ie. FB sends back response instructing javascript in client browser to use "connect" plugin not "disconnect" plug-in.
One more thing. One month ago I have created a FB profile (http://www.facebook.com/pages/Openarchitecture/125515934292877) of the page and have done some updates to this profile. So maybe FB decided that the page (being referenced from FB profile) has now earned the provilige to be "liked".
Like I said at the beginning. Problem solved, but no lesson learned.
For me, the problem (Like popup disappearing after a second; "Plugin","disconnect" response) was happening when the Like button URL redirected to another URL.
The fix was to add og:type, og:url, and og:title (required per https://developers.facebook.com/docs/reference/opengraph/object-type/website), then running the URL through the Facebook debugger to clear the cache (https://developers.facebook.com/tools/debug).
More at https://stackoverflow.com/a/16597060/2391566 .
I implemented the like-button on the page http://www.racket-center.de on every subpage of this site. I noticed that it didn't show up on every page so I tried different implementation-versions (html5, iframe etc) but it didn't work. If I remember correctly the more I tried the less pages the button appeared on.
Now the button doesn't show up anymore – not even within the wizard at http://developers.facebook.com/docs/reference/plugins/like/ You can try it yourself: if you enter the URL of the site + then change another option to get the wizard checking the url the like-button will disappear.
I tried to debug via the linter and fixed some minor warnings it complained (e.g. adjusting the og:image-size to fit 200x200px) but that didn't bring back the button.
I guess the page is kind of blacklisted but I don't know + if it was blacklisted I don't know why.
Does anybody have a clue what might be going on here or kind point me to any resource about fb's blacklists?
Would be nice to get some help.
Thx,
Michael
We are using a facebook like button on a gallery page. When you click the like button, the parent page information is provided instead of the "item" information - but when the link is shared individually on facebook, it pulls the right information.
I tried using Facebook's debug tool, and it pulls the correct information.. the issue seems to be when its on the page. I've checked the meta info and it all looks right...
Any ideas?
https://developers.facebook.com/docs/reference/plugins/like/
Put in the correct sub-link and generate the like button again > Test it first, directly in the like button generator.
If the data is shown correctly in the debugger, then i am pretty sure the problem is that you don´t use the correct/same link in the like button. It would be important to see your usage of the like button. It´s possible that you have an escape character problem, so only the basic link is used.
I've implemented a very simple "like guard" for a facebook tab, and am running into an issue with my test users. Multiple testers are reporting that when they open a tab and click the "like" button, they do not always get a page refresh (so the like guard does not disappear until they do a manual reload). This is using facebook's like button at the top of the page, not one I've coded up myself.
As a sanity check, I enabled some simple logging on my server and have been able to recreate the issue - I hit "like" or "unlike" but there seems to be no request made to my index.php page, so definitely no refresh happening.
I'm aware of this old bug https://developers.facebook.com/bugs/228778937218386 but this one seems different. For starters, after the first click of the "like" button, if I just continue clicking unlike/like/.... then the refresh happens automatically, as expected. What's especially weird is that if I reload the page after the first failed refresh, the refreshes start working again as expected, ie the first update to my like status triggers a page refresh.
Some possibly (?) relevant info:
My Tab is part of a test page, and is unpublished
I am only using http hosting for the tab content, since my https isn't set up yet
So far I've just tested with other admins - so maybe user role affects this?
Curious to see if anyone has run into this issue before.
Finally settled this problem, sharing in case others run into the same issue:
My confusion was caused by where I created/assigned my testers. I made a dummy community page to host the tab I was building and I added all my testers to the test community page. I realized that the only users not getting the weird refresh problems were those testers who I had also added as admin/testers for the app itself. Apparently, adding them as testers to your community page is not enough, and rather than giving you some kind of warning when they view your tabs, testers just get this buggy refresh behavior.