NextScripts
Forum Replies Created
-
Most probably your browser is doing that. Please clear it’s “Saved Forms” data or try another browser.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Getting banned on most platfomsFrom FAQ: https://www.nextscripts.com/faq/
“Is it safe to use?” question
Question:
Is it safe to use?
Will my social networks accounts be suspended if I autopost?
Is it some kind of Blackhat SEO tool?
Can I use it for mass postings?Answer: SNAP is not a spam tool. SNAP is not a Blackhat SEO tool. SNAP is not a tool for bypassing any rules of the site where you are autoposting. You need to follow all terms and guidelines of any site or social network you are working with.
None of the networks we support suspend accounts simply based on the fact that you are autoposting there. Do not post spam or content that is not allowed, do not post more posts then allowed, do not abuse the network in any other way and it will be fine.
If you account got suspended for abuse/spam or any other reasons, please contact the social network directly, we can’t explain why that happened.
Most of the networks (Facebook, Twitter, LinkedIn, Google+, etc..) act on user reports. It means if people are clicking “Report as SPAM” buttons on your posts, you will soon start receiving notices and account suspensions. It really doesn’t matter for them how your posts got there manually or automatically.
It’s a Facebook’s bug.
Please see here: https://wordpress.org/support/topic/forced-to-post-as-visitor/page/2/
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitorHere: 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.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Possible plugin conflictPlease go to the plugin settings and exclude your backup from post types allowed for autoposting.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Latest UpdateMost probably the is issue is %SURL%. Twitter creates “Twitter cards” for your site. When you use %SURL% you give twitter, some other third party site, not yours.
Please try to change %SURL% to %URL% and see if it works.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitorThe only solution is to wait for Facebook to fix it. They are doing something. Some accounts are already fine, some still have it.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitorJust 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.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Completely Borked: what happened?I click and NOTHING happens. No edit options for FB, no dropdowns
Could you please elaborate on that. What does it mean? Can you click on plugin items in the left menu? Will it open plugin pages? If yes, can you hover configured network in the account page and click [Show settings]? Will it show settings? Etc…
What exactly is not working?
Also tt sounds like you have Javascript broken on your sites. Please take a look at your debug console in any browser for Javascript errors.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitorIt 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
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitor“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.
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Forced to post as visitorThe 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”.
Facebook finally disabled an ability to post as a member to even public groups. You must be an admin at the time of plugin authorization to be able to post.
Insufficient permission to post to target on behalf of the viewer
If you are getting this error, Facebook does not think you are an admin of the page or group where you are trying to post. There is nothing we can do. Please check everything.
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 work, otherwise you will see this error.
Thanks for your review.
So your request for the one new very specific feature that only you need and that we actually did put (specifically for you!!!) on our “to-do” list is a “bad support”?
What exactly we had to do to not be considered as terrible company? Just drop everything and implement that feature overnight?
Forum: Plugins
In reply to: [NextScripts: Social Networks Auto-Poster] Can’t authorize Facebook accountFrom:
https://developers.facebook.com/docs/facebook-login/security#surfaceareaEnforce HTTPS for OAuth Redirects and SDK APIs. This setting requires HTTPS for OAuth Redirects and pages getting access tokens with the JavaScript SDK. All new apps created as of March 2018 have this setting on by default and you should plan to migrate any existing apps to use only HTTPS URLs by March 2019. Most major cloud application hosts provide free and automatic configuration of TLS certificates for your applications. If you self-host your app or your hosting service doesn’t offer HTTPS by default, you can obtain a free certificate for your domain(s) from Let’s Encrypt.
Looks like for new apps it’s not just a default setting but also a no way to change it. Your only option is to migrate your to https. (You need to do that anyway, since Chrome will start marking http sites as “unsafe” in 3-4 months)