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 .
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.)
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 developing an app that makes posts on behalf of our users to Facebook. Within those posts, we want to put links to external (non-Facebook) websites.
Looking at the links in the status bar of the browser (usually Chrome), the correct URL is displayed. However, Facebook seems to wrap the actually-clicked link into some extra bells-and-whistles. Usually, this works correctly.
Sometimes, however, this URL wrapping ends up sending the click to a URL like:
http: //spywaresite.info/0/go.php?sid=2
(added space to make it non-browsable!) which generates Chromes severe warning message:
This happens very occasionally on Chrome, but very much more often in the iOS browser on the iPhone.
Does anyone have any pointers as to how to deal with this?
EDIT
For example, the URLs we put in the link is
http://www.example.com/some/full/path/somewhere
but the URL that actually gets clicked is:
http://platform.ak.fbcdn.net/www/app_full_proxy.php?app=374274329267054&v=1&size=z&cksum=fc1c17ed464a92bc53caae79e5413481&src=http%3A%2F%2Fwww.example.com%2Fsome%2Ffull%2Fpath%2Fsomewhere
There seems to be some JavaScript goodness in the page that unscrambles that and usually redirects correctly.
EDIT2
The links above are put on the image and the blue text to the right of the image in the screenshot below.
Mousing over the links (or the image) in the browser shows the correct link. Right-clicking on the link and selecting "Copy Link Address" gets the fbcdn.net link above (or one like it). Actually clicking on the link seems to set off some JavaScript processing of the fbcdn.net link into the right one... but sometimes that processing fails.
I'm not 100% sure what you're asking here, but i'll tell you what I know:- are you referring to this screen on Facebook?
(or rather, the variation of that screen which doesn't allow clickthrough?)
If you manually send a user to facebook.com/l.php?u=something they'll always see that message - it's a measure to prevent an open redirector
if your users are submitting such links, including the l.php link, you'll need to extract the destination URL (in the 'u' parameter)
If you're seeing the l.php URLs come back from the API this is probably a bug.
If links clicked on facebook.com end up on the screen it's because facebook have detected the link as suspicious (e.g. for URL redirector sites - the screen will allow clickthrough but warn the user first) or malicious/spammy (will not allow clickthrough)
In your app you won't be able to post links to the latter (an error will come back saying the URL is blocked), and the former may throw a captcha sometimes (if you're using the Feed dialog, this should be transparent to the app code, the user will enter the captcha and the dialog will return as normal)
If this isn't exactly what you were asking about please clarify and i'll update my answer
Rather than add to the question, I thought I'd put more details here.
It looks like the Facebook mention in the original title was mis-directed, so I've removed it.
We still haven't got to the bottom of the issue.
However, we used both Wireshark and Fiddler to look at the HTTP traffic between the Chrome browser (on the PC) and Facebook. Both showed that Facebook was returning the correct URL refresh.
Here's what Wireshark showed:
What we saw on Fiddler was that our server is issuing a redirect to the spywaresite.info site:
We are working with our ISP to figure out what is happening here.
This happens on any web browser. When I go to the page, I see the like button not showing any counts. Then I...
Press on the Like button.
I then see the box say +1.
I refresh the page.
I no longer see the +1 and I see the Like button as if it was never pressed.
I can repeat steps 1-4 endlessly with the same results - I never see the total live count.
It would seem like it's not keeping counts, but when I query it via:
https://api.facebook.com/method/fql.query?query=select total_count,like_count,comment_count,share_count,click_count from link_stat where url='https://www.myswebsite.com/'&format=json
I see the live stats - so I know it's working. I've also tried different variations of http://developers.facebook.com/docs/reference/plugins/like/ - and old versions as well. I've isolated the code to just be the facebook code with nothing else on the page. For some reason, when I use https://www.myswebsite.com/ it doesn't show. I try other URLs like http://www.google.com with the code, and it works fine, I can see the count.
It's an SSL web site. Does this have anything to do with it? Also, when we initially launched the site with the Like button, it was http://mywebsite.com originally. Then we switched it to http://www.myswebsite.com, and then setup a SSL wildcard to function with both. I'm not sure if caching has anything to do with it.
Thanks!
This blog post might give you some help. What the post says is that you can "sort of" clean your URL with Facebook URL linter tool
Also there is a bug reported related to this issue
I think I have the same issue as here, but can't quite get enough out of the answers over there.
I'm using a Like button (in an iframe on a Static XFBML page) to allow users to Like a YouTube video, with the intention that since the user clicks Like it shares it to their Wall.
What happens is that they click Like, it says "You like this", but nothing is posted, and then after a random short interval the Like button is replaced by a Confirm hyperlink.
What I really want is no "Confirm" stage because a) it's clunky and b) the user has probably left the page by then. I know there's at least one app that does it... Is this behaviour possible for me to code, and if so, how?
this is a feature of the like button, so as to avoid spamming website that cheat user on the like buttons. The "confirm" feature will be turn on for suspicious site. When your site is well received and get positive feedback, the "confirm" feature will be removed automatically.
In your case it's because you implemented it using an <iframe> - I've tried it before and the <iframe> is the cause.