I have a facebook 'Send' button that is supposed to allow a users to post one of my blog posts on my rails-based site to a facebook feed.
This is the real url that I'm trying to post:
http://50.62.12.222/projects/1/blog_posts/1/blog_post_replies
At first I thought it might be an issue with authentication for that particular object's 'show' action. Once I fixed that and verified that the page does not require authentication, I am baffled about what to try next.
neither the route <%= project_blog_post_blog_post_replies_url(#project, b) %> or the rendered url(above) work. And the error I'm getting in equally ambiguous:
"We encountered the following error when sending your message:"
EDIT: And I get the same failure if I try this url on the facebook developer site as well (where it gives you the paste code for the button).
Try setting og meta tags too. Although the are not required fields, but facebook might be failing initial requests for Send button hit. Consider following suggestions
Inferred Property: The 'og:url' property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property: The 'og:title' property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property: The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.
Tiny og:image: All the images referenced by og:image must be at least 200px in both dimensions. Please check all the images with tag og:image in the given url and ensure that it meets the minimum specification.
Once you are done, go to http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2F50.62.12.222%2Fprojects%2F1%2Fblog_posts%2F1%2Fblog_post_replies and ensure you are doing everything fine.
Related
Facebook doesn't get correct description for an image on share for URLs that are DNS web-alias.
See http://anon-chat.thibaultjanbeyer.com/
Inferred Property The 'og:url' property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property The 'og:title' property should be explicitly provided, even if a value can be inferred from other tags.
Inferred Property The 'og:description' property should be explicitly provided, even if a value can be inferred from other tags.
The Facebook object debugger gives:
Based on the raw tags, we constructed the following Open Graph properties
og:url http://anon-chat.thibaultjanbeyer.com/
og:type website
og:title anon-chat.thibaultjanbeyer.com
og:description Your user agent does not support frames or is currently configured not to display frames. However you may visit the page that was supposed to be here
og:updated_time 1435088030
Is there a workaround for this?
Your URL does not have any Open Graph tags that are visible to our crawler (see here).
Add the tags and you should be fine. If you have no control over the HTML at http://anon-chat.thibaultjanbeyer.com/, you're out of luck.
I have a page Yummitube . If I share any link of the webpage on Facebook than no image thumb appears. My og:image is ok.
Let's say url is: http://www.yummitube.com/?id=936
Meta og:image is the folowing:
The image is accesible.
Moreover Facebook linter shows that my og:image is ok.
but what I paste http://www.yummitube.com/?id=936 in facebook no thumb appears.
Any ideas? I tryed to use different sizes of image but that did not help me.
Your link in Open-graph debugger: https://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.yummitube.com%2F%3Fid%3D936
Problem found: The parser's result for this metadata did not match the input metadata. Likely, this was caused by the data being ordered in an unexpected way, multiple values being given for a property only expecting a single value, or property values for a given property being mismatched. Here are the input properties that were not seen in the parsed result: 'fb:admins'
Two solution found:
Trim admins string because most probably it is generating some extra
space
Provide og:type
I have recently finished my site http://wwww.cute-or-not.com
When I share it on Facebook, no meta info or image comes through even though I have set this in WordPress using SEO Yoast. Am I missing something obvious
http://wwww.cute-or-not.com is most likely not what you want, maybe you meant http://www.cute-or-not.com
Using the debugger, http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.cute-or-not.com%2F
More Than One OG URL Specified: Object at URL 'http://www.cute-or-not.com/' of type 'article' is invalid because it specifies multiple 'og:url' values: http://www.cute-or-not.com/, http://www.cute-or-not.com/.
You are defining the OG meta tags twice. Remove it from the "Easy Facebook Share Thumbnails" plugin.
Having issues getting Timeline to work. It is a two part problem.
First, there is an issue of caching parts of the OG metatags. When the debugger goes to my URL, I know it is hitting it correctly because the og:url it spits back is correct which means it has been processed on my end (ex: I send it to og.php?og=read&chapter=799, and it will spit back the right book_id for the og:url, meaning my script processed it). But all the other information seems to be cached. I originally and erroneously had an fb:app_id and og:site_url for an object, so I removed those. The output still shows those as having an existing site_url which is throwing an error. Having a fb:app_id forces the og:type of 'website', which I have set (correctly) to my namespace and object. When I try to POST the action, I get an oAuthException error back, that an og:type of 'website' isn't valid for an object. Once again, that should be fixed, but it keeps caching the old OG data. I have tried adding ?fbrefresh=1, but that did nothing.
Another issue, possibly related...even though I know it got there, and my script processed the request, Facebook doesn't report that. When I click on "See exactly what our scraper sees for your URL" it shows the authentication URL (see below)! As though, it never got there and the popup was initiated, which isn't even how the code for og.php works!! My guess is they got that from the base domain name itself (exmaple.com) before trying the full request with example.com/og.php.
window.parent.location='https://www.facebook.com/dialog/oauth?client_id=164431733642252&redirect_uri=http%3A%2F%2Fapps.facebook.com%2Fexample%2F%3Fpage%3D&state=064bd26ff582a9ec7c96729e6b69bbd2&canvas=1&fbconnect=0&scope=email%2Cpublish_stream%2Cpublish_actions%2C';
I figured it out. I thought the og:url was the URL you wanted people to use to get to the correct page in your app, like an action link. It is, but it isn't. I now have it match the OBJECT_URL you send to timeline.
I had a different URL (an action link to the app), which when redirected, can't be reached by the crawler because it is inside the applications authorized wall. This caused the og:type of website, and data to appear cached.
To fix it, the object_url I post to timeline, and the og:url in the metatag is the same. But you can figure out if it is the crawler or the action link by looking for the query string: ?fb_action_ids=SOME_ID which is sent from link on the timeline. If it contains that, then I forward it to the application page needed from there.
I'm having similar problems to you. It kept complaining about og:site_url being set, even though I never set those. It appears that the error messages it sends are actually inaccurate, and the problem is not that og:site_url is being set, but that the og:url is different from the object url. Sometimes a wrong error message is worse than no error message!
A further question is why an object url has to correspond to a live page that a user will see. An object is a logical unit, but it doesn't necessarily correspond to a single user-visible page. Your redirection trick might work, but it is not the proper way to do something. When I post an action related to an obect, the object url should be used to draw the information of the object, but I should be able to send the user somewhere else. If this was an intended design I think it is a mistake.
I'm having a weird experience with fb sharing. Whenever me or anyone share's my blog post, in the description area my ad codes are visible. This is hammering my adsense. I tried using facebook debugging tool and I got the following issues but I am unable to resolve it. Any help would be highly appreciable.
Errors That Must Be Fixed: Body Meta: 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.
**Warnings That Should Be Fixed: Inferred Property: The og:url property
should be explicitly provided, even if a value can be inferred from
other tags. Inferred Property: The og:title property should be
explicitly provided, even if a value can be inferred from other tags.
Inferred Property: The og:image property should be explicitly
provided, even if a value can be inferred from other tags. Inferred
Property: The og:locale property should be explicitly provided, even
if a value can be inferred from other tags.
It sounds like the meta tags are in the wrong place but because you haven't given us a link to your site it's hard to be sure; they should be in the section of the page. This would be causing the first error.
The second error refers to missing tags, but they might be 'missing' by virtue of not being in the correct place, so fix the first problem first
{edited after seeing your page}
The main error at the top is because you've a
<meta name="alexaVerifyID" content="{snipped}" /> tag outside the <head></head> section of your page.
The rest of the errors are because you haven't added any open graph tags at all - each page should have meta tags telling Facebook what title/description/image to use when sharing, as well as which app/user should be allowed to see the analytics and insights information for the shared links
For more information on how this works, see https://developers.facebook.com/docs/opengraph/
If you want to just get up and running quickly, try the tool at Step 2 of the Like Button Documentation to generate some sample tags