1. plus B Avatar plus B
  2. Typo3 Extensions
  3. pb_social
  4. Issues

Facebook request failed: (#10) To use 'Page Public Content Access',

Issue #17 resolved
Cornelia Eder created an issue

Hi

When I install your extension and run the scheduler task + cronjob i get this error: "[pb_social] facebook: request failed: (#10) To use 'Page Public Content Access', your use of this endpoint must be reviewed and approved by Facebook. To submit this 'Page Public Content Access' feature for review please read our documentation on reviewable features: https://developers.facebook.com/docs/apps/review."

When i want to add the Page Public Content Access in the Facebook Developer App Dashboard i have to provide two screenshots to them.

Facebook.png

But i don't know what to upload here, because I can't see the social stream (Because i get this error)

Do you have troubles with something like this too?

Best regards,

Conny Eder

Comments (21)

  1. Michael Grundkötter

    I did upload a screencast showing the console output. The app review was declined, the response was (German):

    Aus deinem Screencast ist nicht ersichtlich, wie die Verwendung dieser Berechtigung das Nutzererlebnis in deiner App direkt verbessert. Leider konnten wir das auch nicht feststellen, als wir deine App manuell getestet haben. Sämtliche Berechtigungsdaten müssen sichtbar innerhalb deiner App verwendet werden. Wir akzeptieren keine Berechtigungsanfragen für Daten, die du unter Umständen erst zu einem späteren Zeitpunkt verwenden möchtest.

  2. Lars Wilbert

    Same here - Send a Screencast with a similiar overview and another from the console - App was also declined.

  4. Robert Becker

    This only occurs with newly created API keys (since version 3). Old API keys (version 2) still work without a need for a review.

  5. Christian Ehret

    Same here. I even sent some screenshots to Facebook and discussed with them. I did not get any reasonable answer. They said: you do not need public Content Access for that and that my Screencast is not ok :-(

    Did anyone find a solution for that? Even in the graph Explorer I got the message that I first have to get a review :-(

  6. Michael Sieber

    Hello, do we 've any update regarding this issue? We are still facing the reported case. Thank you for any feedback.

  7. Arun Chandran

    Hi Team,

    I've checked with the Facebook developer team regarding the issue. They told me that we need only "manage_pages" permission to display the social wall. And I got that approval. But the extension still showing need permission "Page Public Content Access". Could you please check and give me a feedback.

    Thank you.

  9. Benedikt Wiesnet Account Deactivated

    Hi all,

    for anyone who has the same error message. Private developed API Keys are NO LONGER ALLOWED TO FETCH COMMENTS AND REACTIONS. I made a workaround in this typo3 extension by setting this typoscript options:

    plugin.tx_pbsocial {
    facebook {
            requestParameterList = picture,created_time,full_picture
        }
    }
}

    A more harder workaround is to change FacebookAdapter.php on line 273 on wards with:

    $faceBookRequestParameter =
                        'picture,
                        created_time,
                        full_picture';

    Hopefully this will help someone. I am not sure if this extension is still developed?!?!

  10. Matthias Leiser

    @Benedikt Wiesnet The TypoScript code does not work. But if I change the FacebookAdapter.php as described, then it works! I would also be interested if the extension is still further developed!

  12. Jan Kleuser

    I was facing a similiar problem a few month ago. My App was created after the release of FB-Graph-API-v3. I was developing a Slider that get it’s contents from Twitter and FB. For Facebook the only way I could receive posts was to generate a page access token withe the access token debugger tool from facebook (and of course extend it to the maximum of two month). As I developed this social slider, I read that it should not be possible to automaticly refresh that tokens. So actually it works, but I have to exchange the Access token every two month manually.

    Maybe this information helps to create the fix 🙂 , because I’m really looking forward to use this plugin in future 🙂

  13. Benedikt Wiesnet Account Deactivated

    Yes I can confirm that, but probably with graph api v3 it happens simultaneously. Sometimes Page Access Token is required and sometimes appid and app secret are working. This is crazy I confirmed that by the facebook debugger tool.

    BUT: If I use page access token sometimes only 5 posts are loaded, when clearing cache and retrying it, all posts are loaded…

  16. Rico Mahr

    Hello, could someone help with ths issue?
    I can’t get a test setup working (TYPO3 9.5.7, Plugin 1.4.0, App created with manage_pages and Page Public Content Access). What should I do, to get a preview of the posts for a screencast?
    Thanks in advance

  17. Cripa Mariyam Mathew

    Hello team,

    Could you please follow up this issue to give a solution? Am still blocked with the permission of Page Public Content Access while using this plugin for Facebook.

    Please help to sort out this case.

    Many thanks in advance!

  18. Tobias Hümmerich

    Hello,

    i`ve tried to get my app reviewed, but Facebook states clearly that we don`t need the ‘Page Public Content Access’ because for our use case the rights ‘Manage_Pages’ are enough! Is it possible to change the extension in that way? Did someone already do that?

    Here the statement in german:

    Danke für die Einreichung. Im Rahmen unserer Prüfung haben wir festgestellt, dass deine App für die im Screencast gezeigte vorgesehene Verwendung keinen Zugriff auf öffentliche Inhalte von Seiten benötigt. Das einzig berechtigte Interesse für den Zugriff auf öffentliche Inhalte von Seiten ist das Erfassen und Analysieren von Insights anderer Seiten, von denen du nicht Administrator bist.

    Die gewünschte Funktionsweise deiner App ist bereits durch die Berechtigungen „Manage_Pages“ oder „Read_Insights“ gesichert. Weitere Informationen zur bestmöglichen Nutzung dieser Berechtigungen erhältst du unter folgendem Link (https://developers.facebook.com/docs/facebook-login/permissions).

    BR,
    Tobias

  19. Fabian von Ellerts

    Hello,

    Maybe this will help someone, my request was rejected first and accepted after making a few changes:

    • Two request texts need to be written. The first one is a technical one which is also where you upload the screencast. There:

      • Describe how you login to TYPO3, download, upload and configure the plugin and insert it into a page. Show this whole procedure in the screencast.
      • The docs here feature a text you can use, copy the technical part from there and replace “typo3berlin“ with your page.
      • List all credentials to the page. I recommend creating a separate admin account for Facebook.

    • The second one is an objective explanation how you use Facebook’s data. You can split it into 2 parts:

      • A technical one where you show how the plugin works and mention that the website visitor does not interact with oder login to Facebook.
      • A small text where you describe what your company does with the feed and why you don’t just use the Page plugin.

    Best regards,
    Fabian

    ‌

  20. Ben Abbott

    I ended up moving over to pxa_social_feed as it supports using the Facebook “manage_pages” permission properly, unlike pb_social which seems to be built around requiring the “Page Public Content Access“ (which is way too powerful for a mere social feed).

    I applied for “manage_pages” on eight different websites, all of which I have been granted permission for. None of them were granted “Page Public Content Access“, because it’s too powerful. This extension needs to downgrade its requirements if you want to have a chance at showing a Facebook feed on your site.

  22. Log in to comment
Assignee
Type
bug
Priority
blocker
Status
resolved
Votes
7
Watchers
15
Jira: the preferred issue tracker for Bitbucket. Join the team!