When I like an URL on the company website:
http://guidepal.com/escape/10
The link that gets liked into the timeline looks like this:
=">http://guidepal.com/escape/10?fb_action_ids=10151400567746110&fb_action_types=og.likes&fb_source=timeline_og&action_object_map=%7B%2210151400567746110%22%3A10151100366393350%7D&action_type_map=%7B%2210151400567746110%22%3A%22og.likes%22%7D&action_ref_map=%5B%5D&code=AQB2NUbRhNvppL1HOqmJM6CBGQa1N3vUoK9QrPNNm516895czzIFYn93tiT4HWmBcCCrjK8tYvHqUPLAbu4mhk-xT3w17UMeTITQGnJXW3_NuyYc1Aa7FHl0nTwyuYzDS05x761boSwsGNoOpcL-ulsmiiVObacATa2NQEjLtQFrygJ81fHrSyr7pF5WWlPsf9w#=
The URL is there but there seems to be a problem, since it's adding some more stuff (which I really hope is not an access token there somewhere :P).
I'm guessing there is something wrong with the meta tags, but I have no idea what since everything seems to be okay.
Any ideas?
I've actually investigated this a bit further and this actually is because what is happening on the server side. I'm not responsible for the web-page here, but the one who is, explained that there are some bits of code that handles integer at the end of an url, he would not thought it would be a problem.
Weirdly enough it works by pressing the image instead of the URL in the recent activity.
And a hard problem to know when you are not responsible for both.
I've just liked it, and the URL came up correctly on my Timeline.
It also looks like the meta tags are set up correctly - you can check them on the linter tool that Facebook provides
Related
Hey this is probably a stupid question. Our organization is currently working on a replatform and we are almost done! At this point we're just fixing tiny bugs, like this one.
If I were to copy/paste this URL into Facebook, it would supply the correct title/description for the article automatically: http://prod-www.startribune.com/isle-royale-wolf-population-plummets-to-three/300340911/
However if I were to copy/paste THIS url into facebook, it would choose the first text it encounters after the start of the section of the page it scrolls to. http://prod-www.startribune.com/isle-royale-wolf-population-plummets-to-three/300340911/#comments
The only difference in the URL's is the addition of #comments to the end.
What I'm wondering, how would I have the #comments URL provide the same title/description that is pulled into facebook that the page does when you go to it sans #comments fragment?
Do I just need to redeclare the meta tags in that part of the page?
The issue seems to be that there really isn't an issue. All of the URLs generated for canonical and og:url are pointing to what, ultimately, will be the home for the articles, but currently those URLs don't exist yet. I have a feeling this will be a non-issue once the replatform code goes live.
I've came across this page https://www.tumblr.com/examples/share/sharing-links-to-articles.html which shows a possible way to customly create a share URL for tumblr.
Simplified version of what they have:
Click to share
http://jsfiddle.net/m5ow6bhs/2/
This will take you to the log in page or straight to the share page if you're already logged in. However, if you change the http%3A%2F%2F part to a simple http:// it will now load to a "Not Found Page". http://jsfiddle.net/m5ow6bhs/3/ What the hell Tumblr?
Do you guys have any idea what's going on or what's the correct code to share something to Tumblr?
Cheers.
As with most share services, the URL should be passed as an encoded string. This supports the OPs comments about http%3A%2F%2F(encoded) and http:// (raw).
Tumblr provides variable transformations in the theme operators to handle encoding, but sadly it doesn't work with custom variables.
One quick solution is to drop the http:// part. Example: http://jsfiddle.net/L9jd8dhz/
I have discovered as of recently that the share URL needs to be updated as such:
https://www.tumblr.com/widgets/share/tool?shareSource=legacy&canonicalUrl=<-urlencode(share_url)->&posttype=link
The &posttype= seems to be a new requirement to make the share work correctly.
I've been at this for almost 3 days straight and now I can't even think clearly anymore.
All I'm trying to do is to get my featured image thumbnail to appear when I paste the link in Facebook.
I'm using the Wordpress Facebook Open Graph protocol plugin which generates all the correct og meta properties.
My thumbnail images are 240x200px which respects the minimum requirements and also respects the 3:1 ratio
I've made sure there's no trailing slash at the end of my post URLs
When I use the Facebook Object Debugger, the only warning is in regards to my locale, but that shouldn't affect it.
Facebook appears to be pulling the right image, at least the URL is correct, but the image appears as a blank square
I've gone through pretty much every thread I could find in forums, but all the information available is about using the correct og tags, which I believe I'm already doing.
Thank you very very much for any help, I'm desperate!! :)
You can troubleshoot the OpenGraph meta tags with the Debugger https://developers.facebook.com/tools/debug - this can at least show if you're using the meta tags properly and if Facebook can 'read' the image.
I finally figured out that the root of my issue was the fact that I was using an addon domain (which is really a subdomain being redirected to the top level domain) and I read on eHow (of all places :) ) that Facebook has trouble pulling data from redirected domains.
Not sure if there was another way around it, but I simply ended up creating a seperate hosting account and everything is loading properly now.
one problem youre going to run into testing is that often the first time your page or post gets liked, fb keeps whatever img it finds in your meta tags or by searching your page. so, you'll keep changing your img meta tag and still it wont show the right pic. it's very anoying. One way to get around it is to change the slug of your post. now, it has a different url and to fb, it's a different page. The downside is you lose all the likes that go with your orig url. Not a problem with a new site.
I ended here googling another problem. Maybe this might help someone:
Please bear in mind that the facebook scraper works asynchronously and will need some time (during my tests around 10 minutes) to be able to display an image after seeing it for the first time.
For more information, here's a more thorough answer on a similar problem.
Indeed, as Andy Wibbels points out the FB debugger is a really handy tool.
I faced a similar issue with a server's og:image tag pointing to a secure subdomain which actually mirrors a CDN server,
<meta property="og:image" content="https://subdomain.pathToImage.jpg" />
<meta property="og:image_secure" content="https://subdomain.pathToImage.jpg" />
The FB debugging tool allows you to see the errors that FB encounters when trying to pull the image.
In my case the subdomain was not registered under the SSL certificate used by the HTTPS protocol. Hence FB was getting the following error,
Curl Error : SSL_CACERT SSL certificate problem: unable to get local issuer certificate
A few days ago these type of links worked: http://www.facebook.com/pages/132456789?sk=app_132465798465 but now they give 404's.
The alternative is link to the namespace of the page like so: http://www.facebook.com/pages/foo/1456798324564?sk=app_134654689794 however to find out the link I'd need to ask Facebook for it, and it seem like since the namespace can change I can't just ask for it once.
Is there another way to use page and app id's to link to tabs without needing the roundtrip to Facebook?
I don't think that first format was ever used on Facebook, i'm surprised it worked.
As far as I can tell the 'name' part of a page URL is arbitrary, so just filling in something there will work, e.g.
http://www.facebook.com/pages/Tea/194040780316?sk=info
will also work as
http://www.facebook.com/pages/some_random_text/194040780316?sk=info
I have a facebook like button on each of my wordpress blog posts, this worked fine up until about 2 weeks ago, and now all recent blog posts don't have functioning like buttons.
This is the response I get when I click the like button (post link)
for (;;);{"__ar":1,"payload":{"requires_login":false,"success":false,"already_connected":false,"is_admin":false,"show_error":false,"error_info":null}}
and for the old blog posts that DO work (post link):
for (;;);{"__ar":1,"payload":{"requires_login":false,"error_info":null,"show_error":false,"node_type":"ExternalLink","node_id":"xxxxxxxxxxxxxxxxx","edge_type":"ExternalLinkLike","connect_text":0,"success":true,"already_connected":true,"user_profile":{"name":"xxxxxxx","profile_url":"http:\/\/www.facebook.com\/xxxxxxx","pic_square":"http:\/\/profile.ak.fbcdn.net\/hprofile-ak-snc4\/xxxxxx_xxxxxxxxx_xxxxxxx_x.jpg"},"story_fbid":"xxxxxxxxxxxxxxxxx","is_admin":false,"admin_url":""},"invalidate_cache":[0]}
I've tried replacing the like box code, removing the href attribute from the like box tag, running each link through Facebook URL Linter and none of this has worked!
I don't understand why it works for old blog posts and not new ones, there are no differences between them (that I know of).
This issue has nothing to do with your code. It is a FB issue I encounter on my websites as well. Did some research and came up with this:
this behavior is intermittent, may work on some pages, may fail on others
if you go on this page: http://developers.facebook.com/tools/lint/ and enter your url there, first time it will show up an error, afterwards the page will load. Hit some refreshes and afterwards the like button on your site (on the entered url) will suddenly start working... Very weird! I think it has something to do with FB crawler and (maybe) when accessing the lint tool you somehow force the crawler to recheck your page or something.
If anyone finds out something else, please share, the issue is really annoying...
Looking at the forums here:
http://forum.developers.facebook.net/viewforum.php?id=53
It looks like several other developers are running into the same issue. Some posts there also brought up having to use the lint tool to get their like buttons to work. I've also gotten it to work on my site by just mashing the Like button until it eventually accepts it so like what hpuiu said, i'm pretty confident that this problem's on their end.
Edit: And maybe on a related note, another post said that FB stopped scraping their site until they used the lint tool on their page and another said that they seem to consistently get this issue for any new posts that're around for less than 24 hours.
You could try to add the Iframe version of the like box instead of their javascript version. Sometimes it actually works better when loading multiple post for example.
Facebook doesn't like the '/' at the end of the url. So you can use something like this to omit the '/' at the end of the url :
$title = get_permalink();
<fb:like href="<?php echo substr($title, 0, -1); ?>" layout="button_count" width="300" show_faces="false"></fb:like>