How can I retrieve all comments from a post? - facebook

In this public sandbox group I created a post and added 55 comments on it.
Then I tested in the Graph API Explorer (limit 2 just to make it easier to see the results).
The problem is that there is a next entry indicating that there are more results. But if I click it, it does not show me the next page, instead some odd behavior occurs.
Then after that if I click previous it show me the last page, skipping everything in the middle. If I click previous again, it still shows me the last page with the odd behavior.
To reproduce:
Go to Graph API Explorer
Click Get Access Token ("read_stream" scope is required)
Click submit
Then try to page though all results...
Am I doing something wrong? Or is it a bug?

It was a bug confirmed by a Facebook Platform Team member on December 9, 2013 at 8:08pm and then marked as solved on March 18 at 7:45am.
Bug on Facebook Support
Now fixed.

Related

Facebook - click on a like button does not increase the like count

After searching the internet and doing my own research on this subject I still can not find the answer to my problem, so here it is.
When I click the like button (to like my website http://openarchitecture.cz) then the like count is not being increased.
Debugging the FB javascript code on client-side (in Chrome) and examining the ajax response
send back from FB servers after the click on "Like" button, revealed that FB is instructing the Like button to be "disconnected", resulting in the behaviour described below.
The term "disconnected" is a strict FB term (in a sense of a javascript code), it means that on client-side there will be used a "plugin" that will perform certain operations leading to "inactivity" of like button. Technically, when the plugin "disconnect" is beeing recognized as part of the ajax response, there is an array of predefind actions (functions) that will be followed and called sequentially.
Now for the reproducibility of the problem.
Go to http://developers.facebook.com/docs/reference/plugins/like and fill the "URL to Like" field with http://openarchitecture.cz
url.
Click "Get code", then click "Ok" on the pop-up and finally click "Like" button on the right.
The like count should increase. Instead a pop-up shows up for (aprox.) 1 sec.
then the popup disappears. Now I am in the same state as before I click the
like button, i.e. like count is not increased.
I have found similar questions here on SO, but none of them seems to finally
resolve the issue.
The related questions here on SO are:
1. http://facebook.stackoverflow.com/questions/5195183/facebook-like-button-flashing-on-then-off/12958474#12958474
2. Facebook Like button does not work on one website?
One of the suggestions was that this migth actually be a FB bug. I found a (very recently created) bug, reported in FB bug tracking system. The bug is located here:
http://developers.facebook.com/bugs/268340209965207?browse=search_512b8e0bed9724580954683
The bug has however "Low" priority an so far it does not seem to be resolved (it might even be returned as not a FB issue, I am not sure if this possibility is still open).
So for all interested in this.
Is this a real FB bug ?
How have you dealt with this ?
Could it be that my site is for some reason on FB spam/black/"whatever nasty" list ?
Well. This will end up like the other posts, i.e. no lesson learned here.
[The term "page" used later in this post represents the http://openarchitecture.cz page]
I just tried today to like the page again via the FB generated like button (on http://developers.facebook.com/docs/reference/plugins/like/ ) and the result is now ok. So the like count gets increased after clicking the like button.
The difference that I observed when checking the request exchange to FB servers is that this time the communication has been done (by default. i.e. using the XFBML version of the like button) over iframe, not direct ajax call (as was in the past for XFBML).
I dont know what was the cause (I tried the pure iframe version of like button before) but the response going back as a result of the mentioned iframe request is now correct, ie. FB sends back response instructing javascript in client browser to use "connect" plugin not "disconnect" plug-in.
One more thing. One month ago I have created a FB profile (http://www.facebook.com/pages/Openarchitecture/125515934292877) of the page and have done some updates to this profile. So maybe FB decided that the page (being referenced from FB profile) has now earned the provilige to be "liked".
Like I said at the beginning. Problem solved, but no lesson learned.
For me, the problem (Like popup disappearing after a second; "Plugin","disconnect" response) was happening when the Like button URL redirected to another URL.
The fix was to add og:type, og:url, and og:title (required per https://developers.facebook.com/docs/reference/opengraph/object-type/website), then running the URL through the Facebook debugger to clear the cache (https://developers.facebook.com/tools/debug).
More at https://stackoverflow.com/a/16597060/2391566 .

Stopped Working: FB.ui with method: 'feed' suddenly quit working

This question is similar to: Facebook Error 191 on canvas app using FB.ui() for the 'feed' dialog (worked before, stopped working last week) which was never answered.
Starting today, after the user likes the page and enters the contest, the share dialog which presented itself stopped working and gave:
API Error Code: 191
API Error Description: The specified URL is not owned by the application
Error Message: redirect_uri is not owned by the application.
when logged in as an admin and just an error occurred for other users. This tab has been running well for a while now. I have confirmed it with an associate of mine. They did make a change to another part of the app (yesterday and today) but the sharing was still working until this afternoon. They did not change the part that generates the dialog.
The tab is: https://www.facebook.com/MedjoolDates/app_355398587864294
Anyone have any insight? Feel free to use 'cancel' rather than sharing and fake data to sign up, then unlike the page if you wish.
Thanks in advance.
David
Same problem here, there is a bug posted on Facebook Developes here:
https://developers.facebook.com/bugs/273845842724431
Can't help much without seeing your code.
One thing to check, make sure your redirection_uri is exactly as your domain registered with FB and that you include a trailing / ie http://www.myurl.com/ rather than http://www.myurl.com
I can't answer why it changed, but I had that error fixed by the above change before.
I am having the same issue. Am developing a new app with FB.ui feed functionality, which worked OK yesterday and today it gives the same error as OP.
Went back and checked an > 1 year old app with the same functionality; same error. I cannot see any other solution, than the FB dev team has changed something and not given notice.

Like Button broken on URL "http://www.facebook.com/apps/application.php?id=APP_ID"

Like button (iframe / like.php plugin) of our Facebook app is broken for some days.
We have choose to use "http://www.facebook.com/apps/application.php?id=APP_ID" url instead of "http://apps.facebook.com/APP_NAME/" format (maybe not a good idea).
A click on it leads to a failure (popup telling "There was an error liking the page. If you are the page owner, please try running your page through the linter on the Facebook devsite (https://developers.facebook.com/tools/lint/) and fixing any errors.")
Linter is able to find that http://www.facebook.com/apps/application.php?id=APP_ID must be converted to "Final URL : http://apps.facebook.com/APP_NAME/"
Redirect Path section says "Final URL is in bold (this is the URL we tried to extract metadata from)" and final URL is correct (http://apps.facebook.com/APP_NAME)
But in this case, linter is not able to scrap Open Tags included into "http://apps.facebook.com/APP_NAME" despite the fact that open tags are well recognized if final URL "http://apps.facebook.com/APP_NAME" is directly submitted to linter.
It seems that open graph tags of final url are no more used.
Can someone confirm me that this a new behaviour/bug and tell how to solve it ?
Could I migrate our likes from one url (.../apps/application.php?id=APP_ID) to a new one that works (.../APP_NAME/) ?
Many thanks
Those /apps/application.php URLs were deprecated in December 2011 and removed in February 2012 - you shouldn't still be using them, they automatically redirect to the app's canvas or website URL. Like buttons may have given some semblance of still working on those URLs for a few months afterwards, but effectively anyone clicking them was becoming a fan of nothing
Your like button or Like Box should be pointing to the Page for your app if you have one. That blog post has instructions for creating one if you didn't migrate between December 2011 and February 2011
If you don't have a page for your app, there's no purpose to accumulating fans via the Like button as you can't target ads to them or send them updates.
There's instructions for creating a Page in the blog post i linked above, or in the Communicating with your users doc.

Tab Content Does Not Refresh After First Click of Like Button

I've implemented a very simple "like guard" for a facebook tab, and am running into an issue with my test users. Multiple testers are reporting that when they open a tab and click the "like" button, they do not always get a page refresh (so the like guard does not disappear until they do a manual reload). This is using facebook's like button at the top of the page, not one I've coded up myself.
As a sanity check, I enabled some simple logging on my server and have been able to recreate the issue - I hit "like" or "unlike" but there seems to be no request made to my index.php page, so definitely no refresh happening.
I'm aware of this old bug https://developers.facebook.com/bugs/228778937218386 but this one seems different. For starters, after the first click of the "like" button, if I just continue clicking unlike/like/.... then the refresh happens automatically, as expected. What's especially weird is that if I reload the page after the first failed refresh, the refreshes start working again as expected, ie the first update to my like status triggers a page refresh.
Some possibly (?) relevant info:
My Tab is part of a test page, and is unpublished
I am only using http hosting for the tab content, since my https isn't set up yet
So far I've just tested with other admins - so maybe user role affects this?
Curious to see if anyone has run into this issue before.
Finally settled this problem, sharing in case others run into the same issue:
My confusion was caused by where I created/assigned my testers. I made a dummy community page to host the tab I was building and I added all my testers to the test community page. I realized that the only users not getting the weird refresh problems were those testers who I had also added as admin/testers for the app itself. Apparently, adding them as testers to your community page is not enough, and rather than giving you some kind of warning when they view your tabs, testers just get this buggy refresh behavior.

Facebook like button gives an error: This page is either disabled or not visible to the current user

The like button on my site was working fine and had more than 270 recommendations but suddenly they disappeared and when I click on the button, it gives an error:
This page is either disabled or not visible to the current user.
I checked my URL on the debug tool but it gives me the same result each time that appears to be fine.
I have no idea what is the problem or if my site has been blocked by them.
How can I check if its blocked or find the problem?
My URL is: iran.us
Check this link: http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Firan.us
As for your counts, you specified
http://iran.us (http://graph.facebook.com/http://www.iran.us)
and the counts you're looking for are under
http://www.iran.us/index.php (http://graph.facebook.com/http://www.iran.us/index.php)
The fix for this is your plugin code.
Add data-href="http://www.iran.us/index.php" to the plugin code and it will be back to the old like count. You will not be able to move the 6 current ones over though.