Forced to post as visitor

The only solution is to wait for Facebook to fix it. They are doing something. Some accounts are already fine, some still have it.

After re-authorised today the problem was fixed!

@nextscripts Do you have a support ticket number or forum post on the Facebook side that we could reference for this issue? I’m trying to switch to using your plugin for our social media auto-posting, but I need to be able to post as page before I can make the switch. I realize it’s not an issue on your end, but you seem to have some sort of communication channel open with Facebook.

@cmaverick Are you still experiencing the issue or has it resolved for you as @mariosagathokleous reported?

I just installed the SNAP plugin yesterday, hence my first authorization was after 3/21 and my token is subject to this issue according to @nextscripts previous post. I’m hoping with more information I can push for a resolution in some way, or at least have confidence that it will be resolved.

It’s fixed for me (I commented as such, but it is back a page). Didn’t mark resolved because some people seem to still be having issues.

@cmaverick whoops, sorry I missed that. Thanks for replying. Guess I just have to wait ??

Here: https://developers.facebook.com/bugs/348344542325933/

There is also a hidden non-public conversation between our developer and FB support person.

It’s kind of hard to keep issue open and keep talking to them now, since all our accounts are already fixed.

@cmvaerick I just tried and looks like its fixed now. Looks like they have been FB updating stuff since last data breach.
Anyways Thanks @nextscripts for keeping us updated.

I just added a FB account and it’s not working for me. I tried reauthorizing as well.

Same problem over here. This is a huge problem…

Far as I can tell there are certain APIs which were disabled due to the API abuse which made the news. Accessing the graph API I was able to get the access_token for Graph API Explorer which works when posting to a page.

If you change “Get Token” and specify the page you’re trying to access and specify the following…

GET -> /2.12 -> /<page_id>?fields=access_token

Click submit, test using access_token from the result and you’ll notice this works when using NextScripts.

The problem here is Facebook, they’ve temporarily disabled key features of the API. Facebook needs to fix the issue before people start abusing Graph API Explorer.

Same here
Still a problem
Error 200 randomly returned
Absolutely no auto posts or comments are going through

Same problem here. I hope you can fix it soon.

Unfortunately this fix is not up to us. Facebook must fix it and they are taking their time.

Please see here: https://www.nextscripts.com/news/2018/04/facebook-problems-and-changes/

Hey guys,

I guess ill throw in my 2 cents.

I actually haven’t been active in my posts since December last year, due to a rethink in my posts and planning the upgrade of my site.

Due to this, I never really kept up with the changes of Facebook and SNAP.

The plugin had a very old API and was basically dead in the water.

So today, what I did was delete my old App and recreate the App.

I followed the Instructions to ensure I didn’t miss anything, I even had to make my site HTTPS coz API’s from Facebook force HTTPS now.

and once I was done, I really didn’t pay attention to the “where/who to” drop down. So My test posts were going into the Visitor Area as my actual Facebook.

Once I found out I must change to post to my Page, thats where this threads issue remains.

Despite all my settings set up correctly, it still posts to as my actual Account to the Visitor Section and not as my Page, on the Page.

You will see by this post date that it still hasn’t been resolved.

So far, the plugin has had no error, so I assume its Facebook that is messing up.

I have two accounts. One is working perfectly and another one is posting as my personal name to the community section.
I did some investigation. It looks like you need a special page token in order to post to pages as page name. SNAP correctly requests this token. Facebook correctly returns this token for account #1. For account #2 in exactly the same situation it returns this:

“message”: “(#200) Access to this data is temporarily disabled for non-active apps or apps that have not recently accessed this data due to changes we are making to the Facebook Platform. https://developers.facebook.com/status/issues/205942813488872/&#8221;

No token comes along with this message. As I see in the code, SNAP has a failsafe that reverts back to user token in case of page token is not returned by Facebook. That’s why SNAP is still posting, but posting as user, not as page.

It looks like nothing can be done, until Facebook finishes with it’s “changes to the Facebook Platform”.

PS: Both my accounts and Facebook apps were created at the same time and used with SNAP to post the same data to two different pages. I have no idea why one account is still working and another one is “temporarily disabled”.