been having real issue with using comments and like buttons on pages like http://staging.bangstyle.com/haircut-detail/?uid=2139&img_id=15231
Facebook doesn't like the "?"
Is there a way to force the url on Facebook? I tried using HTTP URI to get the url but still the url shared on facebook stops at /haircut-detail/
Should i invest time on creating htaccess for these files or a different way that i havent tried. Permalinks and php http uri don't work.
Facebook has no problem using "?" in the URL.
I tried your url in the Facebook debugger https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fstaging.bangstyle.com%2Fhaircut-detail%2F%3Fuid%3D2139%26img_id%3D15231 it works but is picking up an issue with your head and/or meta tags
You have tags ouside of your . This is either because
your was malformed and they fell lower in the parse tree, or
you accidentally put your Open Graph tags in the wrong place. Either
way you need to fix it before the tags are usable.
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.
So we have a series of movie trailers that we have been embedding in Facebook, and they worked up until the recent changes. This means, when you embedded them, they displayed an image and you could play the video.
Now they suddenly stopped working. I have gone over the Open Graph tags, and they seem correct, but obviously something is missing.
Do you see anything with this link that is in error http://www.totaleclips.com/test-Player/Facebook.aspx?eclipid=e95147&bitrateid=267&vendorid=1011&FB=1
Any advice is appreciated
This may not be the only/core issue but your og:url tag is pointing to http://www.Image-Entertainment.com which means Facebook will go to THAT url and take the tags from there - the og:url tag should point to the canonical URL for a piece of content
In this case, if it's just a test it should probably point to http://www.totaleclips.com/test-Player/Facebook.aspx?eclipid=e95147&bitrateid=267&vendorid=1011&FB=1 - in production it should probably point to whichever URL is the permanent URL for the video, that URL must have the correct meta tags (also).
You should run your URL through the Facebook debugger - it may not always be entirely clear what the issue is (especially where there's HTTP or og:url redirects taking place) but it shows what Facebook is detecting on your page
Am having difficulty with the url for the facebook comment and like plugins. if I put in a simple url like "www.example.com" it works fine but my app is on a subdomain and uses querystrings to differentiate between different page states. So a sample url would be something like "facebook/example.com/index.php?id=001". However it appears facebook doesn't like this and keeps saying it is unreachable.
I can't believe facebook would limit the scope like this. Someone else must have encountered this. Any suggestions?
Facebook posts have an id something like 123456789012345_123456789012345.
The part prior to the underscore is the page id. The part after is the post id. The URL would be https://www.facebook.com/pageid/posts/postid, or https://www.facebook.com/123456789012345/posts/123456789012345.
Check your URL in Facebook's Debug Tool and this will show the tags Facebook is detecting on your page -in particular check your og:url tag isn't ommitting the URL parameters
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.
We are working on a facebook-app with lots of dynamic pages. As the app is embedded in a tab on a facebook page, the urls contain a get-parameter to address the correct tab/app. We want to implement like- and send-buttons for several pages within our app, but facebook seems to dump all get-parameters from urls within facebook. As the result all like- and send-buttons point to the facebook-page itself instead of the tab.
Does anybody now any workaround? We already tried redirects via an external sefor facebook urls only.rver but facebook seems to evaluate the links on click of the like-/send-button (and seems to follow all sort of redirects).
UPDATE:
Here is an example of a problematic url:
https://www.facebook.com/smartmobil.de?sk=app_171502639574871
UPDATE:
The problem seems to be independant of url get-parameters. It seems that the like-button does not work with any url starting with www.facebook.com
When used in a like-button everything behind the ? will be dumped. This seems to happen for facebook urls only.
Best workaround so far is to point your like buttons at external (non-facebook canvas) urls.
To make this work, you need to do some conditional redirecting to get the user back into your canvas URL. You can either use a client side javascript redirect:
<script>
window.location = 'http://apps.facebook.com/yourcanvasname/foo/bar';
</script>
Or you can do a server side redirect based on the useragent string. Basically, if the useragent contains 'facebookexternalhit' then render a basic HTML page containing OG tags, if not, redirect to the canvas URL.
Doing this means the Facebook sharescraper/linter won't follow any redirects back to the canvas URL, but any user that arrives at your URL will get back to Canvas.
i'm too searching for a solution to control the custom page tab's content through a get parameter (app_data). I still don't have a solution but here at least the reason why all www.facebook.com links are srtiped out of get params. Here at bottom the developer explains why.
Unfortunately I don't think what you are trying to do is possible. Posting a like programmatically requires you to specify a Facebook content ID or alias. This won't work for you because tabs to not seem to have an exposed content ID of their own, and instead use the Page's content ID with an additional parameter which you can't use with the graph.
Liking external links and other content that does not have an ID programmatically is prohibited. With an external URL, the first like of an unrecognised URL creates a new Facebook page for those likes to be represented on (which is the issue I've given up trying to fight), but presumably the presence of your Page's content ID alias (www.facebook.com/smartmobil.de) in the url is making Facebook choose you page rather than creating a new one.
The only suggestion I can think of this late at night is to target an external URL that performs a redirect via Javascript, rather than on the server, but Facebook may be wise to that too and I'm afraid I'm going to bed rather than testing it :)