The mutualfriends connection for users is deprecated in OpenGraph v2.0, however it should still work with OpenGraph v1.0 for another year.
I would expect the FQL mutual_friends_count field to work for anthor year as well. However, it seems like it is no longer supported (returns null).
Anybody knows if it is just a bug, or if it is by design?
This bug has been fixed https://developers.facebook.com/bugs/242368225968716/ (May 8, 2014 at 4:34pm)
This query works for an v1.0 enabled app
SELECT name,mutual_friend_count FROM user where uid IN (SELECT uid1 FROM friend where uid2=me()) order by mutual_friend_count
Related
a few days ago I started to experience troubles accessing facebook group data feed using graph api (i am using v2.8 but the results are the same also with older versions).
The graph api call started to return only the first 10 posts in the feed (i.e. the most recent ones) even though no changes were made from my side.
The same behaviour is reproducible also in graph api explorer using /groupId/feed path (I am not passing the 'limit' parameter in the request url). Previously it has been returning all the available posts with paging, etc.
Please note that if I use a pageId instead of groupId all the posts in the specified page are returned correctly - seems only groups are affected.
Can somebody shed some light on this?
Regards
Due to this thread in Facebook Developer Community it looks like a bug.
Here are bug reports:
https://developers.facebook.com/bugs/1316646108368355?hc_location=ufi
https://developers.facebook.com/bugs/1796973007211974?hc_location=ufi
https://developers.facebook.com/bugs/1645827285730392?hc_location=ufi
Looks like after October 2013 breaking changes ADS api is not working fine . Earlier call to url
https://graph.facebook.com/act_{act id}/adcampaigns?access_token={access token}
will return
Values like
{"id":"{value}","frequency_cap":0,"account_id":{value},"name":"{value}"}
But now the output returns like
{"id":"{value}"}
Can some one please confirm ?
This is one of the changes made in the October 2013 breaking changes and is documented on the 'Completed Changes' part of the roadmap
Adcampaign endpoint
Removing campaign_id and include_budget_remaining flag. You must now
specify query params when retrieving information about adgroups. The
only field returned by default will be id. See docs for more detail.
In facebook adgroup API only adgroup_status is introduced as a filed. however, when you issue a query to fetch an adgroup fields, ad_status is also retrieved. what is the difference between these two?
Thanks,
From Facebook PMD group (February 2, 2012):
Question:
Sylvain Eche Hello we found a parameter ad_status in adgroup that is
undocumented
"ad_status": 2, "adgroup_status": 8,
we suspect ad_status = 2 means the campaign is finished Can you update
the doc with ad_status
tnx
Answer:
This is a deprecated parameter which should be
ignored. We will remove it from the API soon."
http://www.facebook.com/groups/pmdprogram/permalink/292366244154051/
we are experiencing some very odd errors in our installation.
Some times out of nowhere Sitecore throws an error:
Assert: Value Cannot be null. Parameter: Item.
The closest i have come to identifying the problem is narrowing it down to either an index or the web database.
Anyway, if I log into sitecore the Item is just missing, i can fix it in 3 ways:
Rebuild the index.
Recycle app pool
iisreset
Does any of you have an idea why this might be happening? We are running Sitecore.NET 6.5.0 (rev. 120706). Any help will be deeply appreciated.
You are describing a system stability issue, so I recommend opening a ticket with Sitecore support (http://support.sitecore.net). This sort of issue is difficult to troubleshoot over Stack Overflow, since we do not have access to your logs and configuration.
When opening the ticket, I recommend using the Support Package Generator which bundles up all the information (Web.config, App_Config files, IIS settings, Sitecore log files) that Sitecore Support needs to troubleshoot the issue. It's a pretty nifty tool.
That said, from what you describe, it sounds like the issue is related to caching. The fact that restarting IIS resolves the issue indicates that the item is in the Web database, but the runtime doesn't see it. You can prove out whether this is the issue by clearing cache using the /sitecore/admin/cache.aspx screen. If your cache is not getting updated properly, you should review your configuration against the guidelines in the SDN Scaling Guide.
Based on knowing you're using the Advanced Database Crawler, your issue may be how you're converting a SkinnyItem to an Item. I've had this issue before. If you look at the SkinnyItem.cs class, there's a GetItem() method to convert it into an Item. You can see it uses the database to get the item by its ID, language, and version number. Its possible that when you publish from master to web, you are publishing a new version # of an existing item and thus the new version exists in the web DB, but the index is not updated and references the old version. So, this GetItem() call would use the previous version # and the item would be null. One way to fix this is instead of calling that GetItem() method, just use your own code to get the latest version of that item from Sitecore, e.g.
Item item = Sitecore.Context.Database.GetItem(someSkinnyItem.ItemID);
Instead of
Item item = someSkinnyItem.GetItem();
Here's an example flow:
Foo item created in master DB as version 1.
Publish Foo to web
Index will pick up version 1 in web DB and put in index.
Any querying code against index will convert the SkinnyItem to an Item via that GetItem() method and will pass 1 as the version #.
Page will load, no error in log
Back in master, create version 2 of Foo and publish.
Index may not get updated right away or even if configured wrong.
Code that looks against index will call GetItem() and still call with version 1 since that's in the index
But when you published, web no longer has version 1, it now has version 2, and thus that specific version of that item Foo is null
Error shows in log
On a similar note, here's a blog post by Alex Shyba (creator of the ADC) on how to sync HTML cache clearing with the index updates. That may help.
I'm currently using iOS Facebook SDK 3.1. To post a feed story to a users timeline, when on < iOS 6, i've been using +[FBRequest requestForPostStatusUpdate:place:tags:]. This works great, except when I attept to tag a friend [such as I would when typing #FRIENDS_NAME on Facebook.com into the composer. I know that I can pass an array of objects to the tags: argument, however, as I expected, also passing nil to place yields an error (#100) Cannot specify user tags without a place tag.
For sake of completion, here's an example of what I was using:
NSArray *tags = #[#(FB_UID)];
[FBRequestConnection startForPostStatusUpdate:#"Friends Name, this is a test"
place:nil
tags:tags
completionHandler:^(FBRequestConnection *connection, id result, NSError *error) {
}];
Now I understand that using this method, it's not possible to tag a friend in my status. However, is there a method, any method, using the graph API to tag a friend in a feed post, the same way it'd work tagging a user on Facebook.com? I've spent the better part of this morning looking for answers, and i've yet to find any solutions. Any questions i've found on it seem to be at least a year old, so I wasn't sure if they were still relevant anyway. Any assistance would be greatly appreciated!
However, is there a method, any method, using the graph API to tag a friend in a feed post, the same way it'd work tagging a user on Facebook.com?
No.
I've spent the better part of this morning looking for answers, and i've yet to find any solutions.
That’s because there are none – Facebook deactivated this feature for posts made via API quite a while ago.
For Open Graph actions, the situation is different – the allow something called mention tagging.