I have a site, registered as an app on facebook (with fb login). The site is in English, and has og:title og:description app id etc in the meta for the pages.
If people Like a page on the site, the description and title is nicely put on their timeline.
But, if they use Facebook in Dutch, they get the title on their timeline, but the description of the article they shared is replaced by 4 times "niet beschikbaar" (that means "not available")
I tried Facebook in German, but there the English description is used....
Is this a Facebook bug? Or is it me? And why only (as it seems) the "error" for fb users using Dutch?
I do have the same issue. The tools/debug lint from facebook does not see any errors.
There is a bug reported, see:
http://developers.facebook.com/bugs/326334460804515?browse=search_51130494eb59c1a06817175
There is no solution there, hope there will be soon.
More information:
Aggregations
Some components of the Aggregations are translated by Facebook, and others are translated by your app.
In general, objects are translated by your app, and strings associated with actions are translated by Facebook.
Aggregation
An Aggregation's title and all of its caption text are translated through the standard Facebook Internationalization process. References to object title and object descriptions are translated by your app.
Source: https://developers.facebook.com/docs/technical-guides/opengraph/internationalization/
I really think it is a bug in the translations.
Greetings,
Kevin Hoekman
Related
Apologies if this has already been asked or if this is a dumb question, but I can't seem to figure out how to localise OG actions and objects and the Facebook documentation has defeated me (again).
Scenario:
I have a single OG action called Like (the same action that FB creates automatically for apps that use the Like button).
I also have two objects: post and comment.
Stories are created by my app along the lines of "{name} likes a post on {app name}". In the activity panel they appear as "{name} likes {title} on {app name}". Note i do not have any OG Stories defined - I'm simply publishing the Like action along with one of the two objects I have created.
What I'm struggling to figure out is, how to localise the "likes a post on" and "likes" part of the stories being published to a user's timeline.
I am already generating the appropriate locale and locale:alternate OG meta tags that the FB scraper uses to build the stories. The two locales I support are en_GB and ar_AR and for the ar_AR locale I also include localised title and description meta tags.
When I publish a story for a test user with the AR locale selected, the story includes the localised title and description text in Arabic however the "likes a post on" and "likes" text is still in English. I've checked the localisation app in Facebook and there are no strings appearing to localise, whilst the localisation section within the app settings only provides areas for the app title and description and locale specific images.
Does anyone out there have any insight in to how I can localise the "likes a post on" and "likes" associated with the publishing of the Like action?
Thanks in advance!
I created a Facebook OpenGraph action (in English), got it approved, translated all the phrases to Spanish and "approved" all the created translations on the Facebook localization dashboard. In addition, I already set the locale metatags of my object urls to es_ES. Still the action always showing in English language.
The translation progress bars still showing at 0% progress even when I have translated all the strings and approved all of them (I am admin for the Facebook app) many times.
Already read all the Facebook localization docs. Anybody got through the same process and know what error may I have made? I don't know what more to do.
Thanks you all.
Try using the localized js URL:
From: //connect.facebook.net/en_US/all.js
To: //connect.facebook.net/LOCALE/all.js
We're running a canvas app that has fully localized og tags. Everything is working well except when users choose to manually copy the facebook app url (apps.facebook.com/mysite) into a post.
When that happens, we want the text in the posted message to be in the user's language. Instead, it's always uses the English text from the og: meta tags.
If I could detect which culture the user came from, I could change those meta tags. However I don't see anything in the request header or parameters that are sent from the scraper to indicate where the user is coming from.
I did see that there's an og:locale:alternate tag I could use to specify other languages the page is available in, but unless I get a second request from Facebook with a locale value I don't see how that benefits me.
How can I ensure the posted title/description is in the user's language?
Must it be done using the Localization section in the Facebook App settings?
If so, is there a way to automate it? Our translation workflow is pretty well established and I don't want to send translators into the facebook app to finish the job.
You most probably need some parameter in the querystring to differentiate the urls.
e.g
http://apps.facebook.com/my_app/en/
or
http://apps.facebook.com/my_app/it/
this parameter will actually set the active language on your app.
And facebook scraper will cache the localized title/ description from the meta tags.
I created a facebook app. It's in English. However I need it to be displayed in German (only if possible) by default. I went through the facebook manuals and, unfortunately, I couldn't find it.
Your thoughts?
UPDATE: Let me show what I want.
I (as an author) need it to be displayed absolutely in German, even any standard facebook label. I already set local to Deutsch (Setting->Advanced->Locale) but it's still in English.
Couldn't find what?
http://developers.facebook.com/docs/internationalization/
Added for question update:
Facebook:
If you're rendering a social plugin in an IFrame, Facebook
automatically translates the text because it's based on the viewing
user's locale.
If you're using XFBML, you need to load the JavaScript SDK in the
appropriate locale for your site. For example, if your site is in
Spanish, reference this script:
//connect.facebook.net/es_LA/all.js
I'm integrating a Like button in the individual blog posts on my company's website ( www.atlas-games.com , blog by CLASSIC Blogger at http://blog.atlas-games.com ... can't use a widget). Unfortunately the metadata isn't passing through, so in Facebook it looks like:
Michelle Nephew likes a link.
Atlas Games: Charting New Realms of Imagination <--website's name, not post title
The item links work correctly on "link" and "Atlas Games ..." directing to the individual post, but it's using generic text rather than the individual post's title, the site name I specified for Facebook, and the image.
Object Debugger comes up with Inferred Property errors for URL, Title, and Image, though I specify them in the header of my page. For some reason Facebook just isn't finding the metadata, seems like. See the report here:
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fblog.atlas-games.com%2F
I'm having trouble posting my code here ... View Source, though, and you'll see the Meta Property tags in the header and the iframe in the post's footer code (commented out right now).
This is the third time over the course of several months that I've spent hours trying to get this to work, with no luck, so it's not a temporary issue. Any suggestions?
It seems like the structure of the HTML might be the issue as it could be stopping Facebook finding the Open Graph tags.
Fixing these validation errors might allow the tags to be parsed:
http://validator.w3.org/check?uri=http%3A%2F%2Fblog.atlas-games.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=0
Also there are some template variables in the OG tags which aren't being replaced with values:
<meta property="og:title" content="<$BlogItemTitle$>" />
I have the same problem on my blog! And I can't even insert html for the facebook like button directly from facebook developers, into my blog, my blogger blog tells me that the html is erred. I think it has something to do with blogger being a google blog and google now having google+. I noticed all my problems began when google+ came out, I think google is possibly screwing up the facebook like buttons on google sites, to gain monopoly through "share on google+" .