Social Posting Made Easy
If you haven’t already checked out the Social Networks Auto-Poster from Nextscripts then you should consider doing so. This plugin takes the tedium out of posting to all of your other social networks. At last count I believe this one plugin can automatically post your blog entries to over 20 different social networks.
Who really has the time to make blog posts, Facebook posts, Twitter Tweets, post to Google Plus, and a slew of other networks every single time you make a post. I know that I don’t have that kind of time. With a few minutes of simple setup for each network you can let this plugin handle all of the hard work for you.
This plugin can also be setup to handle each post differently based upon the needs of those networks. We have used this plugin extensively over the years, as such you can find some of our other posts about it here:
NextScripts: Social Networks Auto-Poster
- Version: 3.6.10
- Author: NextScripts
- Last Updated: 8-31-2016
- Requires: 3.4+ or higher
- Compatible up to: 4.6
- Average 5-Star Rating: 4.1
- Improvement – Support for URLs with spaces.
- Bug Fix – fix for fatal error: Cannot use object of type nxs_Error as array” error
- Bug Fix – “500 error” and “no post no log” issue.
- Improvement – [Flipboard] Flipboard is now part of nxs-api and has new faster API connector.
- Bug Fix – “Cannot use object of type WP_Post as array” error
- Bug Fix – correct 500px instructions link.
- New/Improvement/Bug Fix – Compatibility with WordPress 4.6. WordPress 4.6 comes with new HTTP API that brakes almost all remote requests.
- New – Mouseover on network with filters is showing what filters exactly are active.
- Bug Fix – fix for “output started at line 310” problem.
- New network “Yo” – Send notifications to your users.
- New – Support for “Spin content” in the “New post to Social Networks” form.
- Bug Fix – [StumbleUpon] “Checking” message
- Several small bugfixes for Pinterest, Delicious, Flipboard
Improvement/Bug Fix – [StumbleUpon] Support for StumbleUpon API v 2.0. Post to accounts that were already switched to API 2.0 was causing “Something went wrong – ERROR”