• I have the facebook app built, and authorized. I (Chris Maverick) am the admin of the FB Page (Vox Popcast). However, whenever I make a test post on the WP site, it posts as a “Visitor” rather than as the page itself.

    The posts are also not importing comments from Facebook, but I suspect that might be a sub-issue of the first problem and that once the posts go to the right place, this might fix itself (but I don’t really know)

    WP site: https://voxpopcast.com/wp
    FB page: https://www.facebook.com/pg/voxpopcast/posts

    Any idea why I am being forced into the visitor section?

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 68 total)
  • Thread Starter cmaverick

    (@cmaverick)

    periodically I get this error on the plugin’s Facebook Account Info page under “Where to Post”

    Can't get Page Token. Array
    (
        [headers] => Array
            (
                [strict-transport-security] => max-age=15552000; preload
                [x-fb-trace-id] => GWjt4E4slT/
                [x-fb-rev] => 3745862
                [content-type] => application/json; charset=UTF-8
                [facebook-api-version] => v2.12
                [cache-control] => no-store
                [pragma] => no-cache
                [access-control-allow-origin] => *
                [expires] => Sat, 01 Jan 2000 00:00:00 GMT
                [www-authenticate] => OAuth "Facebook Platform" "insufficient_scope" "(#200) Access to this data is temporarily disabled for non-active accounts due to changes we are making to the Facebook Platform"
                [vary] => Accept-Encoding
                [content-encoding] => gzip
                [x-fb-debug] => zgmXsGoX/OaG1Wqx7sxTluophfB8GaiirUgpdMy8Iiq3tzXY90rgS6Vx7bU6pITFsYSG+gTz/1MGNUNw/QMyKA==
                [date] => Thu, 22 Mar 2018 17:47:21 GMT
                [connection] => keep-alive
                [content-length] => 205
            )
    
        [body] => {
       "error": {
          "message": "(#200) Access to this data is temporarily disabled for non-active accounts due to changes we are making to the Facebook Platform",
          "type": "OAuthException",
          "code": 200,
          "fbtrace_id": "GWjt4E4slT/"
       }
    }
        [response] => Array
            (
                [code] => 403
                [message] => Forbidden
            )
    
        [cookies] => Array
            (
            )
    
    )

    But refreshing the options removes it.

    Plugin Author NextScripts

    (@nextscripts)

    The user who authorizes plugin MUST be an owner of the Facebook app and MUST be an admin of the page or group at the time of authorization. If both those requirements are met it will post as the “page name”.

    same here. pro version 4.1.7

    Plugin Author NextScripts

    (@nextscripts)

    “message”: “(#200) Access to this data is temporarily disabled for non-active accounts due to changes we are making to the Facebook Platform”

    This is some kind of internal Facebook issue that Facebook is randomly throwing to some users for the last 2 days. It usually resolves itself after several hours.

    I’m admin on the fan page and admin to the app but still the posts are going to visitors section with my real usename

    if i disable in fanpage options visitors posting then on snap test post i get:

    Array
    (
    [Warning] =>
    [Error] => (#200) Permissions error
    )
    Array ( [Warning] => [Error] => (#200) Permissions error )

    and i ‘m admin like i say before

    Thread Starter cmaverick

    (@cmaverick)

    The user who authorizes plugin MUST be an owner of the Facebook app and MUST be an admin of the page or group at the time of authorization. If both those requirements are met it will post as the “page name”.

    I am both the page owner and the authenticated user. In fact, as I am only in the setup phase, the page only has myself and 3 friends following it. So I am the admin of the page, the owner of the app and the authenticated user.

    I also tried the disabling visitor posts idea that buy4me tried and had the same result. For some reason the app seems to not realize that I am the admin of the page.

    I also tried deleting the plugin and creating a brand new facebook app just in case (based on other feedback on other posts in this forum). None of that seems to work.

    Any solution about? Or we do something wrong?

    Plugin Author NextScripts

    (@nextscripts)

    It turned out that this is a Facebook API bug. It affects Facebook APIs Version 2.11 and 2.12. The bug was reported and confirmed by Facebook, but they are not so fast on fixing.

    If you have an older Facebook App(v2.10 or earlier), you can use it and it will work fine.

    Otherwise you can only wait for Facebook to fix it

    If posting only images or status is working. On links is the problem..

    Thread Starter cmaverick

    (@cmaverick)

    It turned out that this is a Facebook API bug. It affects Facebook APIs Version 2.11 and 2.12. The bug was reported and confirmed by Facebook, but they are not so fast on fixing.

    If you have an older Facebook App(v2.10 or earlier), you can use it and it will work fine.

    This appears to not be the case.

    I had an older testbed app sitting around that I was able to revert to older APIS. I just tried posting with API 2.10, 2.9 and 2.5 (the earliest I have access to… and it’s expiring next month). All of them seem to have the same issue of posting as me rather than the page.

    2.10 post: https://voxpopcast.com/wp/2018/03/24/test-seven-api-2-10/
    2.10 FB: https://www.facebook.com/voxpopcast/posts/1785024731562717

    2.9 post: https://voxpopcast.com/wp/2018/03/24/test-five-fb-api-v2-9/
    2.9 FB: https://www.facebook.com/voxpopcast/posts/1785008414897682

    2.5 post: https://voxpopcast.com/wp/2018/03/24/test-six-api-2-5/
    2.5 FB: https://www.facebook.com/voxpopcast/posts/1785018858229971

    So it doesn’t seem that rolling the API back works. Something is forcing the the app to post as visitor no matter what version of the API is being used.

    I am using v4.1.7 of SNAP for all of this… is it possible that an earlier version of the plugin is needed to correctly use the old APIs?

    Thread Starter cmaverick

    (@cmaverick)

    Changes at FB seem to have taken effect and this is working now…. at least for me (currently using 2.8API. Haven’t tried updating back to 2.12 yet)

    Still have the issue! I have one website, only one of the two websites seems to have the problem and i can’t post at all at the page.
    I’m getting this error:

    Array ( [Warning] => [Error] => (#200) Permissions error )

    Plugin Author NextScripts

    (@nextscripts)

    Just an update.

    Facebook confirmed that this is NOT a version issue. It’s the time that authorization token was created is an issue. If you authorized the plugin before March 21 st it will post correctly. All tokens created during the authorization after March 21st, will result this problem.

    It seems like Facebook is fixing or at least doing something about this issue, because some users reported it as “resolved” this morning.

    <b>You MUST re-authorize the plugin to get a new token that will work.</b> Existing tokens won’t just start working.

    Ashish

    (@ashishpatel1992)

    It is not yet resolved.
    I have also started facing this issue today. Tried reauthorizing from two different admin accounts. Still not working.
    Please provide some solution.

Viewing 15 replies - 1 through 15 (of 68 total)
  • The topic ‘Forced to post as visitor’ is closed to new replies.