I've seen many posts with similar problem but no concrete solution.
I had 38 likes on my website and one day it was reset to 0. Now I've updated the script (as given on FB website) but have lost all my likes.
How can I get my likes back?
I had 38 likes on my website: http://www.buildingmanager.com.au
According to http://graph.facebook.com/http://www.buildingmanager.com.au/ you got 37 shares right now.
and one day it was reset to 0. Now I've updated the script (as given on FB website) but have lost all my likes.
In your like button code, you have given a different URL,
<div class="fb-like fb_edge_widget_with_comment fb_iframe_widget"
data-href="http://www.buildingmanager.com.au/sfmportal/" …>
– and that URL has only one share (http://graph.facebook.com/http://www.buildingmanager.com.au/sfmportal/)
And putting your base URL through the debugger shows that you’re a) redirecting to the second URL, and more importantly b) have given the second URL as content of the "og:url" meta tag.
If you want your likes from http://www.buildingmanager.com.au/ to show up using the like button for either of those URLs – then you will have to give that URL as "og:url", so Facebook knows you consider this the “actual” Open Graph URL to be liked.
If you are not willing/able to do that, because you want http://www.buildingmanager.com.au/sfmportal/ to be the new, actual URL for your project – then you’ll have a fresh start now, whether you like it or not ;-)
Are you sure nothing has changed at your side. Maybe a redirection? It's very unlikely to have Facebook set your likes to zero. But if there is a very slight at your URL, then it would. Maybe some recent plugin you've installed? Or moved your pages/changed URLs of your posts etc. You may use the Facebook debugger at https://developers.facebook.com/tools/debug for more info about your URLs. Hope it helps, because it's just not logical for Facebook to do such a thing.
I had a similar problem with one of my websites.
It was fixed by specifying that "/index.php" part after the ".com" to get the likes/shares back.
I had the same problem sometime back. The url in the og:url had https://... while the one in the like button element had http://...
They should match.
Related
I'm creating a web app which uses Facebook feed dialog plugin in some pages. When I try to share these pages, the URLs posted to the news feed get truncated.
I'm using the direct URL approach. When the user wanna share something, she clicks in a link that is going to redirect her to the feed dialog. The link is composed as shown below:
https://www.facebook.com/dialog/feed?app_id=MY_APP_ID&link=SHARED_URL&redirect_uri=REDIRECT_URL
For example:
the URL I have in the "link":http://www.simplecity.com.br/DP/Index/?CID=0&UID=1
the URL I get in the news feed:http://www.simplecity.com.br/DP/Index/?CID=0
Has anyone already experienced this issue? Any suggestion?
The usual cause of this is forgetting to encode the link when you pass it into the Direct FB URL.
Are you forgetting to urlencode the link parameter (i'm especially thinking of the &) when creating the URL you're passing the user to?
I recently encountered the same problem with a straightforward link - I inserted:
https://example.com/page.html
into a page post. However, on the page it was rendered as:
https://example.com/page.ht...
as if the last two characters of the html extension were merely not displayed, as indicated by the elipsis. However, if you copy the link from the post you find that those chars are actually missing and the link resolves as 404. If you edit the post and reinsert the link, it is saved correctly, although the 'overflow' characters are still hidden by the elipsis. Very misleading.
What seems to work best is if you use the Facebook Developer OG tags in the page and then use Open Graph Debugger to scrape the link. This puts the URL in the FB realm and it picks up the correct link just fine. As you are doing this, the debugger tool gives you feedback to the effect: "This is the first time we have seen this URL"; which is baloney if you have put the URL on a FB page beforehand.
I have filed a bug report with Facebook; but I am not expecting them to own up to this bug.
Hopefully, someone here can give me some light. I have been researching this issue for a couple of days now, and cannot find a suitable solution.
First of all, I have used the facebook debugger and I understand what the error is, except that I am not sure how to fix it. You can see it here:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.viewrecalls.com%2Fshow%3Fq%3DGuidecraft%2520Mega%2520Profit%25204-in-1%2520Dramatic%2520Play%2520Theater%2520Toys%26amp%3Bu%3Dhttp%3A%2F%2Fwww.cpsc.gov%2Fcpscpub%2Fprerel%2Fprhtml12%2F12131.html
I guess, facebook wants me to use either www.viewrecalls.com/show or www.viewrecalls.com in my og:url tag, as both of them passes the validation; however, if I do that, then the information displayed in Facebook will not be the information from the original link, and the user will be redirected to an URL that is not the original one or intended one. I am not sure how to resolve this issue.
My website queries an API and lists the query results. Once you click on a result from the listing page, it goes to a "show" page, where the details of the item clicked is shown. I have "long" QueryString going and one of the parameters is an URL. The QueryString is however encoded, and everything works perfectly, except that the facebook debugger gives me that validation error, and the button is not showing a count, it only shows 0 even though it posts to my facebook wall.
Any help will be greatly appreciated!
Thanks!
Point your og:url tag (on the URL you're pointing a Like button at) to the URL you actually want the user to like, which has the metadata for that URL - image, title, etc
A circular redirect path almost always means an og:url tag on a page points to another page, which redirects (either by og:url, a canonical ref tag or a HTTP redirect) back to the first page or another page in the redirect chain.
Facebook's Debug Tool should show you the steps followed and where the redirect is
{edit}
In your case, i'm not 100% sure, but it looks like part of your URL has a & encoded in it, which may be the problem.
I manually curl
http://www.viewrecalls.com/show?q=Guidecraft%20Mega%20Profit%204-in-1%20Dramatic%20Play%20Theater%20Toys&u=http://www.cpsc.gov/cpscpub/prerel/prhtml12/12131.html
and get an og:url tag of
http://www.viewrecalls.com/show?q=Guidecraft%20Mega%20Profit%204-in-1%20Dramatic%20Play%20Theater%20Toys&u=http://www.cpsc.gov/cpscpub/prerel/prhtml12/12131.html
which, when i curl THAT, has an og:url of
http://www.viewrecalls.com/show?q=Guidecraft%20Mega%20Profit%204-in-1%20Dramatic%20Play%20Theater%20Toys&amp;u=http://www.cpsc.gov/cpscpub/prerel/prhtml12/12131.html
it looks like another & is being added into the URL each time and recursing - should the ampersand not be encoded in a URL as %26?
I recently changed domain name for my site and migrated my content. Most URLs from the old site use a 301 redirect to the new site, as you would guess.
In an effort to retain FB like and comment data, I kept the og:url property set to the old URL, since it is the original and canonical identifier in Open Graph. I implemented in August, and it was working properly, with previous like data retained. Now it is not working and showing previous like data, and fails in the URL Debugger.
Here is an example from the new site:
http://seattle.findwell.com/million-things-to-do-seattle/washington-brewers-festival-2011
In URL Debuggger, it now returns this error:
There was an error in fetching the object at URL 'http://seattle.findwell.com/million-things-to-do-seattle/washington-brewers-festival-2011/', or one of the the URLs specified via a redirect or the 'og:url' property including one of http://www.hometalkin.com/seattle/million-things-to-do-seattle/washington-brewers-festival-2011/.
Nothing has changed in my OG tags. Has something changed with canonical URL in open graph that causes it to fail when a redirect is in place?
This page:
http://seattle.findwell.com/million-things-to-do-seattle/washington-brewers-festival-2011
has this og:url:
<meta content="http://www.hometalkin.com/seattle/million-things-to-do-seattle/washington-brewers-festival-2011/"
property="og:url" />
but when you actually go to (in fact - when Facebook crawler tries to go to) this URL from og:url the site redirects you back to:
http://seattle.findwell.com/million-things-to-do-seattle/washington-brewers-festival-2011/
This is a circular reference.
In order to fix it you need to change your og:url to:
http://seattle.findwell.com/million-things-to-do-seattle/washington-brewers-festival-2011/
I actually had a very difficult time with this when I was first starting out as a developer.
I made a tool for this exact purpose -- as I thought it might be helpful to others:
Facebook/Open Graph Like Button Generator
It generates (and stores) the open graph tag(s) so you don't need to put them in your page and the 'Redirect URL' tells it where to send all the traffic.
It detects the Facebook bot/scraper too so it won't interfere with anything :)
Good luck
I had exactly the same problem.
I have changed my website url and I have over 40.000 radios with fb likes and comments.
Example:
http://www.radioways.com/fr/radio/nrj.html
to
http://www.radioways.fr/radio/nrj.html
I spend days and days reading and checking the forum and I did not find the answer...
Here is what to do:
1. In the og canonical, you need to put your old website url
2. In the Iframe url, you can put both. The result of the likes, will be the addition of the likes of the ogcanonical + the likes of the Iframe
An this will not work (and this is why I spent so much time USELESS) untill you validate those setup with FB
Best regards.
I am very surprised about this problem. If you check along several web sites, you can see that many times the Facebook likes counter does not show any value, although the link has a count value greater than zero. If you check that thing with the Twitter same service, it always works right. It is a programmer or a Facebook team fault? Exists any way to solve this problem?
Thanks for reading.
I'm not 100% sure what the problem is, but chances are it's Facebook's fault (when in doubt blame them). :)
No, seriously... the Facebook Like plugin has several options that let you determine how the total gets displayed (if at all): standard, count, button_count and box_count. And if behavior is not what is documented and expected, then chances are Facebook is having a buggy kind of day/week/month.
But if you just need to query for the count, then you can use FQL to pretty easily get that info:
http://www.saschakimmel.com/2010/05/how-to-get-statistics-for-a-facebook-like-button-and-shared-urls/
I think it's the default behaviour to sometimes not show the count bubble until someone click on the share button.
Here is a description from another blog and how to get around it.
http://kopepasah.com/social-media/facebook/facebook-share-count-button/
Check for missing ampersands after parameters in like button's "src" url.
As far as iframe box_count type of like button for Facebook Page is concerned
I had the same problem because I manualy pasted fanpage link in to src of like button witohut & or '&' after pageid or page name.
I think that if there is no ampersand later parametrs aren't parsed.
When we first put up a blog post, Facebook often (but not always) gets confused about what the page is. Specifically, if you try to use the Like button on the blog page OR if you try to share via the Share link on your profile, Facebook will see the root blog page rather than the actual post page.
For example, we recently posted:
http://thisorthat.com/blog/2010-song-of-the-year-round-1-results
If the user "likes" it, it returns the title for:
"http://thisorthat.com/blog"
When you run the post URL through the FB Linter, you can see the problem.
"http://developers.facebook.com/tools/linter?url=http://thisorthat.com/blog/2010-song-of-the-year-round-1-results"
In the Debug section it shows an extra og:title, og:url, description and og:image (the last 4 rows of the Debug section). This is the meta data from the root directory. What we cannot figure out is why. Why is Facebook seeing the correct meta data on the page and then also pulling the meta data from the root directory (and using that incorrectly to populate the data for the Like button and the Share URL tool)?
One other oddity. FB "figures it out" after a few days. Of course, by that time relatively few people are viewing the post.
UPDATE -- I want to thank Peter Bailey again for his answer, but we also discovered that there was another issue that we had to resolve before the Like button worked.
The issue was that we were displaying the Facebook the Like button on a post that was not yet published. The problem with this is that FB then can't resolve the URL and "guesses" as to the correct URL. In our case, it always guesses thisorthat.com/blog. Unfortunately, it then caches that guess for a number of days and that cache cannot be cleared by the Linter. So the ultimate solution was to both fix the og:type as Peter suggested, but also to remove the Like button from the blog post preview. It's very important that you don't show FB a page before it's published or if you do, change the URL.
Pretty sure it's your Open Graph type that's the problem.
<meta content="website" property="og:type"/>
Per the documentation
Use article for any URL that
represents transient content - such as
a news article, blog post, photo,
video, etc. Do not use website for
this purpose. website and blog are
designed to represent an entire site,
an og:type tag with types website or
blog should usually only appear on the
root of a domain.