Note that there are some explanatory texts on larger screens.

plurals
  1. POFacebook: FQL for fetching all posts on a managed page throws one of two exceptions
    primarykey
    data
    text
    <p>I am using the RestFB client to fetch all post_ids of a Facebook Page.</p> <p>The query is</p> <pre><code>select post_id from stream where source_id=265813166783408 </code></pre> <p>Where the id if of the page I'm querying. It can be found <a href="http://www.facebook.com/pages/Rowz/265813166783408" rel="nofollow">here</a></p> <p>I initially tried executing this without an access token. This gives a <strong>104: Requires valid signature</strong> error from Facebook.</p> <p>I looked up this error and the solution that many gave on SO is to use an access token. However if I try with an accessToken (with permissions: manage_pages, publish_stream, read_stream, offline_access, read_insights) then Facebook gives a different error <strong>190: Impersonated access tokens can only be used with the Graph API</strong>. </p> <p>Does this mean I shouldn't use FQL for getting page posts. The Facebook documentation doesn't mention anything on these lines but like I said it keeps alternating between these two errors.</p> <p>PS: I can use the Graph API with my access token to fetch Posts but for my specific scenario I felt FQL would be a far better option, since I can nest this query into a query on the comments table (eventual aim).</p> <p>Thank you.</p> <p><strong>UPDATE:</strong></p> <p>Please see Facebook developers for a discussion on <a href="http://developers.facebook.com/bugs/416084548430182?ref=notif&amp;notif_t=open_graph_comment" rel="nofollow">this particular issue</a> If you are using the RestFB library then also see the <a href="https://github.com/revetkn/restfb/issues/34" rel="nofollow">relevant issue</a></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload