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!
Related
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
I'm using facebook open graph to make a custom action like this:
UserName is tagging a Post with MyApp.
It works well, but I have only one problem:
In my recent activities I have:
Bed77 is tagging a Red Gorgeous Post with MyApp.
and in my wall I have:
Bed77 is tagging a Post with MyApp.
"Red Gorgeous Post" is the og:title that I have set for that object in my page.
Why it's fetched only in recent activities and not in the wall?
It's an automatic facebook decision?
Explained with one image:
Thanks.
Yes, the locations of object-type and object-title are determined by Facebook in what are called 'Timeline Units'.
In your example, "red gorgeous POST" (the title) is displayed below the header ("Duccio is tagging a POST with PostBlogger").
Recent Activity has a different format that is more compact.
In OG Aggregation Units you have some control over the display of objects and their attributes. For example, if you have a Trip, you could display the km/miles of that trip with Trip.distance in the Aggregation unit.
I have built several websites, and for some reason none of them will post to my wall anymore when I "like" a blog post, or like the site in general. (Using Iframe) Example:
http://madhatterulti.com/
http://www.reyniersaudio.com/blog/
The funny thing is, I had a friend try it, and it posted to his wall fine. Though, this person did not have timeline enabled, and I do.
Anyone have any ideas?
It appears the "like" appears in my "activity log". By default, the "like" is set to be "allowed on timeline". I am able to change this to "hidden from timeline". This setting implies to me that it should be showing up on the timeline.. yet it is not. Also, I can change the setting to "featured on timeline", but once again, this does not work.
It seems that the way the Like button works has changed (or not really!). I tried liking one of your blog posts and my own website and nothing appeared on the timeline. But reading the Like button introduction:
The Like button lets a user share your content with friends on
Facebook. When the user clicks the Like button on your site, a story
appears in the user's friends' News Feed with a link back to your
website.
And indeed, it appeared on my friend's news feed and ticker!
I suppose we cannot consider the timeline as the new news feed. Because it's not!
AND it seems that there are two ways a liked URL is going to appear on the user timeline which are
1) when the user has something to say, i.e when the user writes something along with the like:
2) if you click on the More Recent Activity block. And allow this activity to appear on your timeline.
Now maybe there are other cases (that I'm not aware of!) for a liked URL to appear in the user's timeline directly (maybe with custom Open Graph objects or a custom Facebook script that would decide for you?).
I linted one of your URLs and it states the the fb:admin and fb:app_id should be specified for better click-thru rates
Like Button Warnings That Should Be Fixed
Admins And App ID Missing: fb:admins and fb:app_id tags are missing. These tags are necessary for Facebook to render a News Feed
story that generates a high clickthrough rate
http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Fwww.reyniersaudio.com%2Fblog%2Frecording-computer%2Frecording-computer-cpu-benchmarks-sandy-bridge-nehalem-and-bulldozer-processors-compared
I have timeline enabled and it did no post to my timeline at all. Strange huh?
EDIT
Based upon some comments from Roeland on other responses:
The funny thing is, this worked about a week ago. It WOULD post to my
timeline. In addition, if I go to my "activity log" it shows that I
liked something. It also supposedly lets me "allow it on the timeline"
which is the setting by default.. yet it does not show up on my
timeline
I'm wondering if it could have something to do with too many people reporting the stories as spam, or the app id was hijacked and used for spam purposes (or the domain/ip being marked as abusive, etc). Maybe this has caused Facebook to become more cautious when "showing" this liked content. ifaour has seen the content on his feed and timeline, however I could not get it to show.
My concern is that no app_id was specified and not admin was specified either. You can reuse the same app_id with many comments/like buttons (contrary to your assertion that you must have a new app id for each like button...not sure where that came from).
1) Paper.li enables people to publish online newspapers from their favorite social media. An example is here : http://paper.li/tag/socialmedia. All the pages are provided in six languages (English, German, French, Spanish, Portuguese, Japanese).
2) For each of these pages, we are inserting OpenGraph meta information in the source of the page as described in Facebook documentation (https://developers.facebook.com/docs/opengraphprotocol/). We insert the following metas :
a. og:title : The paper title inserted by the user on our service.
b. og:description : A standard description for all pages on our service.
c. og:type : We do not used a standard type provided by Facebook here and we know that the page is classified in “Others” by providing the following value “paper_li:newspaper”.
d. og:url : This is the paper URL.
e. og:image : This is the image of the first article shown in the page to the user. (this is the most relevant content for this page).
f. og:site_name : This is top domain of the app, we mean here “paper.li”
g. fb:app_id : This is the Facebook Application Id we use for our service (providing a Facebook Tab App and login on our service too). This app can be accessed through the following URL on Facebook : http://www.facebook.com/362293833600.
h. og:locale : It defines the current language used by the user on our service
i. og:locale:alternate : It defines all the five other languages we support on our service
This meta information is working really well when using the send button or the like button with social plugins.
3) Our service provides papers who are updated every 24 hours on the same URL (each daily edition is served on one unique URL corresponding to the paper). By this, it means that “og:image” can change (that’s 99.9% of cases) daily, because first article fetched on the web will change daily and image too (corresponding to point 2.e). Paper title (indicated in OpenGraph meta by the point 2.a) can be changed by the user at any time too. In this example, the title is in Japanese in the Graph, for example, with always the same avatar picture in the wall posts.
4) As it’s suggested in your documentation, we want to use the publishing functionality from Facebook linked with the “Like” button. By this, it means that every time a paper is updated on our service, our service is publishing automatically a status to the page corresponding on the Graph on Facebook with the daily headlines (article title, description and image) through the GraphAPI. By doing this, every user having liked the page with the “Like” button will get the status in his news feed if Facebook decides to show it. That’s the purpose of the “Like” button and it’s working really well.
The problem is the following: when we access each of these pages liked on Facebook as an administrator (with application authentication token), we can publish statuses (what we are already doing), but they are published with a page avatar corresponding to the first “og:image” meta that was fetched by Facebook at the first “Like” of this page. It means users are seeing an image for this page that is not corresponding to the content (statuses) published by the page. Same problem appears with the title (if a user is changing it on our side, it can’t be updated on Facebook).
We find it very strange as for standard pages (created by “Create a page” button on Facebook), an access to “Profile picture” and page settings is provided as we don’t have it for pages created through the “Like” button plugin placed on our website (even if we are admin of the page through the app_id). The only way for us to change it for future pages is to change “og:image” meta information but it means that no more relevant image will be shared with corresponding URL (when sharing it in a status at a specific time, for example).
In conclusion, our question is the following: Is it possible to change avatar image and settings (title, ..) on Facebook (through Graph API) of a page created (in the Graph) through the “Like” button plugin? What would be the impact of this action?
In conclusion, our question is the following: Is it possible to change
avatar image and settings (title, ..) on Facebook (through Graph API)
of a page created (in the Graph) through the “Like” button plugin?
No, pages cannot be created via the Like plugin. But if you're referring to a feed post being created, then still no because your app did not insert it.
What would be the impact of this action?
If any authenticated app can change people's posts, regardless of which app created the posting, to their feed, then it might lead to abuse of the system.
I'm pretty sure the default title "Publish this story to your friend's Facebook Wall?" is incorrect. When the user publishes the story, it will appear on his and his friends' news feeds, but not on the walls of the user's friends. I'd like to customize the title so that it doesn't contain a lie. Is there a way for me to do that?
There is no provided way to do that. It's possible you could modify the DOM after the showFeedDialog prompt has been created, but you'd have to create your own JS to do that, and it might not be possible within the confines of FBJS.
I'm not sure where you see the problem with the title here however, unless it's a semantic interpretation. The News Feed is a subset of the data that appears on the Wall of a user. When a user confirms a feed dialog that is targeted at a friend, it will create a story on the Wall of the user as well as the Wall of the user's friend (and by extension be part of the respective news feeds as well), hence "publishing the story to your friend's wall".
Wall items do not show up on all your friend's walls... they are your wall items. If a story is part of a news feed, as showFeedDialog facilitates, then the story will be picked up and put into all your friends news feeds... but it is never saved to your friends walls.