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/
Related
I'm using the FB Graph API explorer and version 11.0 I've added the page id, feed and fields. Previously we were using 'link' and 'title' but according to the docs here those are deprecated and these are the new field names:
attachments{unshimmed_url}
attachments{title}
but when I add this to the FB Graph API Explorer I either get the error:
Field attachments specified more than once. This is only possible
before version 2.1
or I only get the first mentioned attachments field (attachments{unshimmed_url})
1234567/feed?fields=attachments{unshimmed_url}&attachments{title}
Can’t reproduce this error right now, using v11.0, but it should work if you just list the sub-fields comma separated:
…/feed?fields=attachments{unshimmed_url,title}
https://developers.facebook.com/docs/graph-api/advanced#fieldexpansion
Edit: Can reproduce, with the “correct” incorrect syntax.
feed?fields=attachments{unshimmed_url},attachments{title} throws this error; you had feed?fields=attachments{unshimmed_url}&attachments{title} in your post, which is a different thing - that’s one URL parameter named fields, and then one named attachments{title}
I'm using the built in Web Service API in Sitefinity 10.
I tried to filter all news items by their related data item/items with Odata, but it seems that it could not be done.
~/api/default/newsitems?$expand={related-data-field}&$filter={related-data-field}/any(c: c/Id eq 888ac18a-85c0-4259-9a3c-05f25e53b23e)
With such a query I get an error with "Value cannot be null.\r\nParameter name: type" message.
Is it even possible to filter by related data item with Odata in Sitefinity? Thanks.
A colleague of mine pointed out that Navigational properties of related types are not supported yet for filtering.
https://docs.sitefinity.com/manage-the-properties-of-a-type
This is now supported with version 14.2.7921.0 of Sitefinity
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
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
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.