search

strohne / Facepager

Facepager was made for fetching public available data from YouTube, Twitter and other websites on the basis of APIs and webscraping.
https://github.com/strohne/Facepager/releases
505 stars 198 forks source link

Facebook graph api v3.2 broken #183

Closed terrok9 closed 2 years ago

terrok9 commented 2 years ago

Getting information from public pages is harder in your last build.

Let's see an example:

Putting a specific seed as Object ID is as usual and works as usual. However, when you fetch data from the path //posts, it returns paging nodes, not data object keys or data nodes.

It would be great if you can show us how to recover an organized database as it used to be.

I will attach some workarounds.

Picture before last build:

image

Picture cn the current build:

image

Thank you soo much.

strohne commented 2 years ago

Hi there...the Graph API v3.2 unfortunately is outdated. If you use the latest Facepager version and/or update the base path to v13 it should work as usual. Can you confirm this?

terrok9 commented 2 years ago

Hello!

Thank you for your answer.

I am following the same steps using the v13, this is to generate a db where you can observe each element of the node 2 as a list of posts, just like the first image that I uploaded.

Is not working as usual due to the fact that it recovers all the posts as a column of the dataframe and puts paging information as relevant data of node 2.

Are we able to recover the same structure that we did recover in v3.2? (posts by post db) Or we should simply process this data externally knowing that is harder to extract per post information.

Thank you in advance for your help.

strohne commented 2 years ago

Sorry, we can't reproduce this. The latest version of FP with the Facebook API base path including version 13 should work. Maybe you can ask the question in the Facepager user group on Facebook and provide step by step instructions how to reproduce the issue?