Latest releases, news and announcementsLatest releases, news and announcements
NextScripts API for Facebook is joining NextScripts Premium API family.
Official native Facebook API was going downhill for quite some time. It used to work fine and it had all necessary features, but during the last year it lost a lot of functionality.
Here is the list of some major changes made by Facebook recently:
– Setup become extremely over-complicated. Facebook setup instruction has 16 steps. Facebook “Common Problems” FAQ section has 22 items.
– Ability to set Image, Title and Description for shared links has been removed, forcing only usage of OG meatatgs.
– Ability to post to Closed and Secret groups for non-admins has been removed.
– oAuth login callback URL field become mandatory, complicating setup.
– oAuth “Strict Mode” become mandatory, complicating setup even further.
– Ability to post to open groups has been removed for non-admins.
– “Enforce HTTPS for Web OAuth Login” setting become mandatory, forcing all sites to switch to HTTPS.
– Ability to post to pages as “Page Name” has been broken. All post are made from user’s name and go to the community section.
– Ability to post to Groups has been disabled complitely.
Basically official native Facebook API become very restricted, very hard to setup and very limited. It’s time to have an alternative. NextScripts API for Facebook could be used to replace official native Facebook API. It has none of the restrictions listed above.
Available today as Beta (supports only Autoposting to Groups) to all active Premium API subscribers and prepaid users. Please update SNAP plugin to version 4.2.2, API to version 4.3.3 and SNAP Upgrade helper to version 1.5.5.
If you still don’t have NextScripts SNAP Premium API for WordPress you can get it here: SNAP Premium API
Facebook recently became a major troublemaker for the SNAP.
Unstable Graph API 2.12
It started with the release of the very buggy and unstable Graph API 2.12. The first thing it broke is the ability to post to pages as “page name”. Posts were posted as personal name and went to the “community” section of the page. Facebook acknowledged the bug and tried to fix it. As of today it’s fixed for most users, but some are still experiencing it. More info about that here.
Graph API 2.12 also removed the ability to post to any groups (even public) where you just a member. Only admins can post to groups.
Graph API 2.12 also tightened up security basically forcing people to switch sites to https (ssl) protocol. It came in form of “Insecure Login Blocked: You can’t get an access token or log in to this app from an insecure page. Try re-loading the page as https://” error. More info about that here.
To make things worse (much worse) right after the release of already unstable Graph API 2.12 Facebook got hit with now famous “User’s data leak” issue. Data got leaked through the misuse of API apps, so Facebook started to shake it down. Right now all apps are getting reviewed and checked for undesired activities. As the result platform become unstable to almost unusable level. Many apps just randomly stop working partially or completely. Some apps lost an ability to be authorized, some can’t post to groups anymore, some can’t post to pages, some apps are getting temporarily disabled.
All kinds of pretty useless error messages are thrown:
(#200) Access to this data is temporarily disabled for non-active accounts due to changes we are making to the Facebook Platform
(#200) Permissions error
(#200) The user has not authorized the application to perform this action.
(#283) Requires manage_pages permission to manage the object
Platform Access Disabled: Access temporarily disabled due to changes to the Facebook Platform.
End of Groups API
As this wasn’t enough today Facebook issued a new statement announcing the end of some API features used by SNAP. It looks like starting today Groups are no longer available though the API at all. It’s also unclear what will happened to pages.
The end of autoposting to Groups comes in form of this error:
We are considering the possibility of creating our own Premium API for Facebook. It won’t be free, but it will be free from all native Facebook API platform troubles and limitations. We understand that ability to post to Facebook Groups is essential for a lot of SNAP users.
UPDATE: We did some extensive research and it looks like it will take us about a week to make our own API for Facebook. The first release will contain only API for posting to groups, then we will add profiles and pages. It also looks like our API WILL NOT have any recent Facebook’s restrictions. It will be able to post to all groups (public, closed, secret) where you can normally post (yes, no “admin privileges only” anymore). SNAP API for Facebook will be available to all active “SNAP Premium API” subscribers and prepaid users.
UPDATE2: SNAP API for Facebook is now available as Beta (supports only autoposting to Groups) to all active Premium API subscribers and prepaid users. Please update SNAP plugin to version 4.2.2, API to version 4.3.3 and SNAP Upgrade helper to version 1.5.5.
UPDATE3: SNAP plugin to version 4.2.2 comes with a potential fix/workaround for “Cannot post as page, Forced to post as visitor” issue.
Facebook Graph API 2.12 came with another huge functionality killing announcement.
Facebook disabled the ability to post to “Public” groups where you just a member in Graph API 2.12 with 90 Days depreciation delay for earlier API versions.
It means that if you made a Facebook App after January 30, 2018, you won’t be able to post to “Public” groups where you just a member. If you made an app before January 30, 2018 you will loose that ability around May 1st, 2018
Facebook is saying “You made an app after January 30, 2018 and you won’t be able to post to “Public” groups” in from of “(#200) The user has not authorized the application to perform this action.” error.
PS: This is really a huge change to official Facebook API. It removes a very popular feature from SNAP. We are considering creating our own API for Facebook that won’t have such limitations.
Your apps currently have access to Graph API v2.5 which will reach the end of its 2-year lifetime on 12 April, 2018
Facebook just sent out announcement about the end of Graph API v2.5.
We would like to remind you that SNAP is 100% compatible with all Facebook Graph API versions from 2.0 to the latest 2.12. Once 2.5 reach its end of lifetime, SNAP will automatically start using the next available version. No actions from you are required.
You can download new API files from https://www.nextscripts.com/mypage
Please see here for instructions: Alternative Instagram Configuration
Instagram made some additional changes to it’s infrastructure Feb 1-5. Those changes were causing some new errors and problems. Please see updated Instagram issues and how to fix them page for the fix instructions.
API 4.0.44 fixes all recent Instagram problems and brings some improvements.
You can download new API files from https://www.nextscripts.com/mypage
* New [Beta] – WPML and Polylang support in Filters.
* New Network – Messenger Line (line.me)
* New/Improvement – [Post Edit] – All changes are saved instantly. No more “Please save the post to apply changes”.
* New/Improvement – [Import/Export Accounts] – There are 4 options now – Export All, Export Selected, Import and replace, Import and Merge
* New – [Instagram] “Default Image” field in settings.
* Improvement – PHP 5.3 compatibility. (It still works better on PHP 5.6 and 7+)
* Bug Fix – [Facebook] & instead of & in the “Additional URL Parameters”
* Bug Fix – [Twitter] Option “Dash” has been removed from “Replace spaces in hashtags with …” because Twitter no longer supports dashes in hashtags.
* Several minor bug fixes.
You can update plugin from your WP Admin panel or download it from https://wordpress.org/plugins/social-networks-auto-poster-facebook-twitter-g/
Initial Version 4 Release. 100% Re-written. New engine. New interface. Existing Posts Auto-Reposter. More info: https://www.nextscripts.com/v4
Instagram made some very big changes to authentication process. About 70% of our users are affected by them. Before the changes the process was quite simple: Sometimes Instagram decided that login from SNAP is "unusual" and asked for confirmation. You just had to open...
Sometimes Instagram decides that login from SNAP is "unusual" and asks for confirmation. Until yesterday, you just had to open Instagram on your phone and tap "This was me" button on "We have detected an unusual login attempt" screen. Yesterday this stopped working....
SNAP for WordPress Version 4.1 has been released. This version adds support for WPML and Polylang in filters and one new network - Messenger Line. It also eliminates the necessity to "Save" WordPress post after making changes to SNAP message format. == Changelog == =...
SNAP for WordPress Version 4 has been released. This is the biggest SNAP update ever. Almost 100% of the code was re-written. - New Autoposting Engine. Faster and 180% more efficient engine. It takes less memory and resources to preform autoposting jobs. - Old Posts...
The final release date for the long awaited SNAP WordPress Plugin Version 4 is set for October 1, 2017. The first closed beta version is available today. The first public beta version will be available on August 31, 2017. Here is the full release schedule: Version 4...