StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8460810
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-12-10T23:40:15.440
FavoriteCount
0
LastActivityDate
2011-12-10T23:40:15.440
LastEditDate
LastEditorUserId
0
OwnerUserId
666611
ParentId
8356450
PostTypeId
2
Score
10
ViewCount
0
LastEditorDisplayName
text
Body
You need to respond to the GET request with a challenge response. I have the same route for both POST and GET requests and use the following code: route: <pre><code>match "facebook/subscription", :controller => :facebook, :action => :subscription, :as => 'facebook_subscription', :via => [:get,:post] </code></pre> controller: <pre><code> def realtime_request?(request) ((request.method == "GET" && params['hub.mode'].present?) || (request.method == "POST" && request.headers['X-Hub-Signature'].present?)) end def subscription if(realtime_request?(request)) case request.method when "GET" challenge = Koala::Facebook::RealtimeUpdates.meet_challenge(params,'SOME_TOKEN_HERE') if(challenge) render :text => challenge else render :text => 'Failed to authorize facebook challenge request' end when "POST" case params['object'] # Do logic here... render :text => 'Thanks for the update.' end end end </code></pre> That should get you going with things... Note that to make a subscription I am using this: <pre><code>@access_token ||= Koala::Facebook::OAuth.new(FACEBOOK_API_KEY,FACEBOOK_API_SECRET).get_app_access_token @realtime = Koala::Facebook::RealtimeUpdates.new(:app_id => FACEBOOK_API_KEY, :app_access_token => @access_token) @realtime.subscribe('user', 'first_name,uid,etc...', facebook_subscription_url,'SOME_TOKEN_HERE') </code></pre> I think the key is that you properly respond to the GET request from Facebook. They use this to verify that they are contacting the correct server prior to sending confidential info about their users. Also -- its been a while since I've looked at this, but if I remember correctly, I seem to recall having issues with anything besides default protocol port specifications within the callback URL. Ex: <a href="http://www.something.com:8080/subscription">http://www.something.com:8080/subscription</a> did not work -- it had to be <a href="http://www.something.com/subscription">http://www.something.com/subscription</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONo POST from facebook using real-time updates in Rails, Heroku and Koala
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USejlevin1
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PONo POST from facebook using real-time updates in Rails, Heroku and Koala
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.