I am quite new to facebook API. I have used the open graph to generate actions and objects.This actions are now validated by facebook.
But, I have a translation trouble : the action and object are necessarily in english. And the facebook doc say that the action and objects are automatically translated when the meta tags are made 'locale', which was done. But my site is french and the actions an objects are still appearing in english. Does anyone can hep ?
(The ref's doc:https://developers.facebook.com/docs/opengraph/internationalization/, http://developers.facebook.com/blog/post/605/ )
Best ,
Newben
If you’re already refering to the documentation – why don’t you read it as well?
The blog post says how translating your app works, and https://developers.facebook.com/docs/internationalization/ describes it in more detail.
Related
I want post some message and tag friends like facebook (web version) does. For example, "simple message #SomeUser". So the question is: how can i tag friends and what is the easiest way to do that?
As i understand there are two ways to do that:
1) https://developers.facebook.com/docs/graph-api/reference/v2.1/user/feed#pubfields but i don't understand why should i provide place id in order to tag friends and where to get (or generate ???) it. Moreover i don't understand where should i get user id. https://developers.facebook.com/docs/graph-api/reference/v2.1/user/taggable_friends? I don't know because request always fails.
2)https://developers.facebook.com/docs/opengraph/using-actions/v2.1#mentions ? I've tried #[userTaggingToken] and replaced userTaggingToken with user id from /user/taggable_friends. But it doesn't work too. Moreover, user id from /user/taggable_friends is much longer than one provided by example.
I abstract from any sdk so please don't refer to any programming language (and its SDK). Any links to documentation and examples with concrete requests (like .../v2.1/user/feed) and data should be passed (message="...") are welcome.
Hello fellow community members,
I was unable to find a helpful answer, so I will give this a try: I recently developed a website that has a FB "Recommend" (same as "Like") button implemented. I have never dealt with this before, hence my complete lack of knowledge.
Now, I implemented the code the FB developer's Like page (--> http://developers.facebook.com/docs/reference/plugins/like/) creates correctly into the website (both the script and the DIV-tag, yet something that is not automatically generated seems to be missing and needs to be added for the button to work correctly. It currently does not post to the FB wall.
Upon doing a debugging check, I received the following results: [...]
Unfortunately, I have no clue what to do with that data. How and where exactly in the HTML code do I implement those missing TAGS and PROPERTIES? Any help would be highly appreciated...
Kind regards & many thanks in advance, :-)
Doc
It looks like you're missing the Open Graph meta tags. Those go into the head of your page.
Facebook has a generator to help you create the tags, but you'll need to add them into your markup.
About a month ago YouTube decided to get rid of it's "tags" from the frontend of their website:
http://youtubecreator.blogspot.com/2012/08/tags-removed-from-video-watch-pages.html
Which also in turn left media:keywords blank through any API feed request as read here:
http://apiblog.youtube.com/2012/08/video-tags-just-for-uploaders.html
The nice thing was for another month or so (until a few days ago) you could still access a video's "tags" or "keywords" through the API by looping through the category term(s)
It seems YouTube has taken that away also and it now only displays ONE category term for each API feed...and most of the time they are the basic YouTube categories like "Music" or "People" etc.
My questions to the YouTube development team is why was this taken away from the API (I understand taking it away from the frontend of the website) and will it ever return in any form to the API?
In the original Creators blog post you guys stated:
"Tags remain an important way to organize and help others find your videos. We strongly encourage you to continue tagging videos -- this will help increase your audience by improving the discoverability of your content."
So if Tags are still important and still utilized for search results...why in the world are they not available through the API anymore?
Any help and/or info would be greatly appreciated as this has completely destroyed the functionality of MANY of my sites! Thank you.
It appears they've made them private and you must use an authorized API request with adequate channel privileges to access them now. This really sucks since I've used them for filtering videos from a channel on a site and making authorized connections to the API via PHP has been complicated for me to get working correctly.
And the fact that this added complication is ONLY for keywords seems a bit ridiculous, but I don't guess the Youtube API team cares.
Unless a WHOLE lot of people complain about it, I doubt they'll add this back as a public.
I just added
Update: This change also applies to <category
scheme="http://gdata.youtube.com/schemas/2007/keywords.cat"> tags,
which were not mentioned in the original announcement.
to the announcement blog post. <category> tags should have been removed for the same reason <media:keywords> was removed, but due to an oversight they were left in unauthenticated API responses for a few weeks. There are no plans to add back keyword information via either metadata field.
If your goal is to have some semantics in the video, Freebase Topics can help. You can for instance do a JSONp call
<script src="https://www.googleapis.com/freebase/v1/topic${item}?filter=/type/object/name&callback=putFBname"></script>
with a small javascript function
<script>
function putFBname(respuesta){
span=document.getElementById(respuesta["id"]);
span.innerHTML=" "+respuesta["property"]["/type/object/name"]["values"][0]["text"];
}
</script>
to get the name of the topic.
Freebase topics come in the API v3.
I'm trying to integrate the Facebook comments left on our site in a way in which the content can be crawled by search engines and also for people (although I highly doubt there will be many) who don't have Javascript enabled on their browser.
Currently our Facebook comments are displayed via the use of the Facebook comment social plugin (using the <fb:comments href="MY_URL" num_posts="50" width="665"></fb:comments> tag). This ends up rendering an iFrame (which are mostly ignored by search engine crawlers) so the plan is to render this information and format it with basic HTML. To do this, the comments are pulled using the Graph API - this is then only be displayed to crawlers and people with Javascript disabled.
This all works nicely using the Graph API call (https://graph.facebook.com/comments/?ids=MY_URL), parsing the JSON result and displaying it on the page. The problem is that the <fb:comments> approach filters our results based on a blacklist we have set up on one of our Facebook Apps. The AppId with the relevant blacklist is stored on the page using metadata (<meta property="fb:app_id" content="APP_ID"/>) which the <fb:comments> control obviously must somehow use to filter the comments.
The problem is the Graph API method does not filter any results as I guess no blacklist (or App Id containing a blacklist) is specified. Does anyone know how to specify a Facebook App ID to the API call URL or of another way to not fetch commnents back that violate the terms of the blacklist?
On a side note, I know the debate about filtering content in comments rages on but it is a management decision to implement the blacklist, and one that I have no influence in changing - just incase anyone felt the need to explain the reasons why content filtering is or isn't a good idea!
Any thoughts on a solution?
Unfortunately there's no way to access a filtered list of comments using the API - it might be a reasonably request to have this in the API - you should file a wishlist item in Facebook's bug tracker
Otherwise, the only solution I can think of is to implement your own filter on your side when retrieving and displaying the comments from the API.
According to the Comments plugin documentation the filter on Facebook's side is implemented as a simple substring match, so it should be trivial to implement.
A fairly simple regular expression match should be able to check each comment against a relatively long list quickly.
(Unfortunately, the tradeoff here is that implementing a filter is easy, but you'd also need to write an interface so that whoever's updating the list of disallowed words can maintain the list for both the Facebook plugin, and your own filtering.)
Quote from docs:
The comment is checked via substring matching. This means if you blacklist the
word 'at', if the comment contains the sequence 'a' 't' anywhere it will be
marked with limited visibility; e.g. if the comment contained the words 'bat',
'hat', 'attend', etc it would be caught.
Pretty sure there is no current way of doing this from the graph API, the only thing I can suggest is taking the blacklist and build your own filter
I'm trying to understand actions and objects on facebook and im completely blown away by how spotify publishes actions with that format. How the heck do you customize the layout of a user's action like that?
As far as im concern, with facebook's lovely documentation, all you can do is publish actions on a single line : (user A) -- (action) -- on -- (object) followed by a title and description.
How do you design html/css layout of a user's actions? Link? Attachment? I'm guessing you have to do some sort of "magic" on the description? Thanks!
Facebook's open Graph Tutorial does a decent job of explaining this but with the various options you have to scroll for a while to make it to the grouping part. In short, the individual actions you're familiar with combine together via "aggregations" which can be set to show a number of formats from lists to grids.
To set one of these up you must configure your Actions and Objects via the open graph settings first and then manually create an aggregation and a few defaults to fill in for preview purposes.
This will show up when a user authenticates your app for open graph and becomes customized to them as they start actually using said actions.
Now as for the play button option, that's something I assume is unique to their integration.
Documents at https://developers.facebook.com/docs/beta/opengraph/tutorial/