FAQ
1.2. I am getting duplicates! What should I do to prevent it?
1.3. How to change default message format?
1.4. Image Errors: “Could not get image”, “Server can’t access it’s own images”, “Error uploading photo” etc..
1.5. Wrong or missing image.
1.6. Not Enough Memory allowed for PHP
1.7. [Skipped]- User ID XXX can’t autopost – Post ID:(XXXXX)
1.8. error:0D0890A1:asn1 encoding routines:ASN1_verify:unknown message digest algorithm
1.9. SSL/https/certificate related issues
1.10. Connection errors like “Couldn’t connect to host”, “Couldn’t resolve host”, “connect() timed out”, “Failed to connect to …”, etc…
1.11. SPAM/unsafe/abusive/suspicious content errors like “The action attempted has been deemed abusive or is otherwise disallowed”
1.12. Nothing is posted and nothing in the log.
1.13. PHP Notice and PHP Warning
1.14. Scheduled Posts are getting published immediately.
1.15. Your temporary folder or file is not writable
2.2. Facebook Error: [Error] => [ERROR] An unknown error has occurred
2.3. Only I can see the posts, nobody else can.
2.4. ERROR:(#200) This API call requires a valid app_id or [Error] => No Auth Token Found/Not configured
2.5. Facebook Error: “The user hasn’t authorized the application to perform this action”
2.6. Error: No appsecret_proof parameter was specified
2.7. Authorization errors like: “Can’t Load URL” or “Given URL is not allowed by the Application configuration”
2.8. Wrong “attached link” or “shared link” description
2.9. Token Issues like “Error validating access token”, “Session has expired”, “Expired access token”, “Not Authorized”.
2.10. I am posting to Facebook Page but all posts appear as my name, not as page name. Is there a way to change that?:
2.11. ERROR: (#1) An error occured while creating the share
2.12. Error:(#100) The status you are trying to publish is a duplicate of, or too similar to, one that we recently posted to Twitter.
2.13. [ERROR] (#1500) “The url you supplied is invalid” and [ERROR] “This link could not be posted”
2.14. What is “Let Facebook fill the link info”?
2.15. Errors: “(#200) The user hasn’t authorized the application to perform this action” and “Can’t get Page Token. NO TOKEN RETURNED”
2.16. Error messages when trying to post to a Facebook group
2.17. I have a video in my post, but when I post to Facebook it’s posted as image preview and it’s not playable.
2.18. How can I change the color of my text?
2.19. Where can I post on Facebook? Should I be an admin of the page/group?
2.20. Can I post to Closed/Secret Groups if I only a member (not an admin)?
2.21. What name will be used on Facebook?
3.2. Wrong image and/or description on Google+ Posts
3.3. Number of photos in album 2000 >= limit 2000
3.4. Error (NXS): Lost Login info.
4.2. Please update your Instagram app to continue posting photos
4.3. It says posted successfully, but link leads to “Sorry, this page isn’t available.”
5.2. Broken reCAPTCHA image
5.3. Linkedin blacklisted my IP address
6.2. Pinterest Error: This pin contains a link or text that we do not allow. We have blocked this pin for your safety.
6.3. Error: Transfer closed with outstanding read data remaining
6.4. Pinterest error: “Sorry we could not fetch the image.”
6.5. Pinterest has your Hosting IP in the list of potentially suspicious networks
7.2. ERROR: Post Rejected. Reddit thinks that you don’t have rights to post here
10.2. Status contains malware
10.3. This request looks like it might be automated
10.4. Twitter error: “Could not authenticate you”
10.5. Why there is no character counter for Twitter? Please add it, it should be easy.
It’s a known issue that we can’t fix. “Google Analytics” and some other plugins hijack the authorization workflow.
Please temporary deactivate “Google Analytics” and/or all other plugins (“Blog Promoter”, “Tweet Old Post”, “Simple Facebook Connect”, “Evergreen Post Tweeter”, “Simple Twitter Connect” etc.. ) related to “Social Networking”, do all authorizations and then activate them back. Even some versions of Woocommerce could cause this.
First of all check if your networks (especially Facebook) are not auto-posting to each other. For example you can link your Facebook to your Twitter account, so all Facebook posts automatically go to Twitter. if you do not remove this, you will get one post on Twitter from SNAP and another one from Facebook.
If this is not your case, please check this link: How to deal with duplicates. WP-Cron: Scheduling Tasks in WordPress
Different question – same answer: How could I reset the “Already Posted” status? . I cloned the post, but I am getting “-=Duplicate=- Post ID: XXXXX Already posted.”
Answer:
Format settings are saved individually with each post. Any changes you make in the general settings page will affect only future postings. if you have drafts and/or scheduled posts they will be posted with old settings unless you change them manually for each post.
If you changed the format for already published post, please don’t forget to save the post before clicking “Repost” button.
UPD: Version 3 has a special button that you can use to reset all existing settings to the current default values.
This error means that at the time of autoposting your image wasn’t set or wasn’t available. Please check that first.
Image must be set at the time you hit the “Publish” button. Some third party plugins that make posts sometimes publish post without featured image and then add it later. If this is your case, you can try to delay the autoposting for several minutes.
If image is set, you can have some kind of protection on your images, (like “hotlinking” protection or unusual “User-Agent” header protection), you can have wrong URLs defined (like relative URLs like /img/mypicture0005.jpg instead of full URLS like http://www.nextscripts.com/img/mypicture0005.jpg), also it could be your server’s DNS misconfiguration, which means your server can’t resolve itself and get the image. Please contact your hosting provider or server admin for additional info.
Update (Summer 2014): Tumblr recently changed the headers for it’s image retrieval bot. New tumblr requests are coming with empty “User-Agent” header. A lot of servers deny empty “User-Agent” requests causing “400 – Bad Request – [0] => Error uploading photo” problem. Please contact your hosting provider to allow such requests. Update 2 (Sept 2014). Twitter is now making empty “User-Agent” requests too.
Update 2: Please see the reply here for a simple test: https://wordpress.org/support/topic/twitter-posts-not-posting-images?replies=11#post-6402194
Please see the full article How the plugin gets images
Short version:
If “Alternative Featured Image location” is set in the settings, plugin will take image from there.
Plugin takes featured image from the post. if there is no featured image it will take the first image from the post body. if your post body has no images it will take the specified default image. if default image is not specified it will take first image from the page.
Please set featured image to clearly define what image you would like to show or specify Plugin Settings->Other Settings->”Open Graph” Tags->Default Image URL for og:image tag for the default image.
Image must be set at the time you hit the “Publish” button. Some third party plugins that make posts sometimes publish post without featured image and then add it later. If this is your case, you can try to delay the autoposting for several minutes.
Important! Some networks (like Google+ and Stumbleupon) ignore all your image settings and take the image specified in the og:image tag, so please make sure this tag is set as well.
Update: Facebook is showing the wrong image?
Facebook has an option “Let Facebook fill the link info”. If this option is selected, Facebook will decide what image to take by itself and ignore all plugin settings. Facebook takes it’s info from og: metatags, so make sure that those metatags are configured on your site. Please see Facebook FAQ #2.14 here for more info
Starting from version 3.0 64MB of allowed PHP memory is mandatory for the plugin. WordPress takes 25-30 MB of memory just by itself. Plugin now supports 21 networks and it takes 5-7 MB
Using it on 32MB websites will just put your site out of memory and kill it’s performance.
If you need some technical details:
Plugin uses this function to detect the memory: $memory_limit = ini_get(‘memory_limit’);
If your server allows runtime php.ini variable changes you can try to put this to the wp-config.php file:
define( ‘WP_MEMORY_LIMIT’, ’64M’ );
Otherwise you need to change it directly in the php.ini file. Please contact your hosting provider or server admin if you don’t know how to do this.
Please see here for explanation and resolution of this: New Security Rules starting with version 2.7.13
The remote connection software you are using on your server might be compiled with a very old version of OpenSSL that does not take certificates signed with sha256-With-RSA-Encryption into account. It requires at least OpenSSL 0.9.8o for a total management of SHA256.
Please contact your server admin or hosting provider about this issue.
* Error setting certificate verify locations: CAfile: /etc/bbbb/cccc/certs/ca-bundle.crt
* Invalid or no certificate authority found
* SSL read: error: XXXXXXXXXXX
* Problem with the SSL CA cert
* [ERROR] SSL connection timeout
* [ERROR] SSL connect error
* Unknown SSL protocol error in connection to …
* Peer certificate cannot be authenticated with known CA certificates
* SSL certificate problem: unable to get local issuer certificate
* Protocol https not supported or disabled in libcurl
* Can’t get Facebook User. Please login to Facebook
* TLS packet with unexpected length was received
* SSL certificate problem, verify that the CA cert is OK. Details:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed.
Please note (this is important): This is NOT about expensive and complicated “Server side SSL certificates”. When your site makes a post it acts like a client, not as a server. This is about free client side SSL. Client side SSL are the same SSL certificates that included in any webbrowser and used to access SSL protected websites via https protocol.
More info: http://curl.haxx.se/docs/sslcerts.html
Unlike Twitter or Google+ that could be automatically switched to non-SSL connections in such cases, Facebook and some other networks require to be accessed by SSL at all times.
Also please see here: How to check if curlSSL is working properly
Update 2:
Recently discovered the shellshock vulnerability in bash required an update that has temporarily broken SSL for many servers running PHP around the web. Fix for bash problem done by your server admin could cause “Problem with the SSL CA cert (path? access rights?)” error.
To resolve the issue, you’ll need to restart Apache (or nginx). If that doesn’t fix the problem, you’ll need to restart your entire server.
Update 1:
Possible solution sent by one of our users:
I think I found the solution for the certificate bundle problem, when trying to authorize Facebook. WordPress installs a version of the ca-bundle.crt file by default, that generates the problem. What I did was downloading another certificate from here: http://certifie.com/ca-bundle/ca-bundle.crt.txt When you copy-and-paste this text into Notepad and save it as a .crt file (instead of a .txt file) and reupload this to /wp-includes/certificates, Facebook will authorize correctly. Hope you find this useful as I ran into this several times with SNAP. And it has nothing to do with SNAP at all
* [http_request_failed] - couldn’t connect to host
* Name lookup timed out
* connect() timed out!
* Couldn’t resolve host ‘graph.facebook.com’
* Operation timed out after …
* Connection timed out after …
* Connection reset by peer
* This IP address is not on the Server IP whitelist
** Failed to connect to graph.facebook.com. Connection refused
** Failed to connect to 69.171.247.20: Permission denied
*** Failed to connect to 2a03:2880:2110:9f01:face:b00c:0:4: Network is unreachable
You need to contact your hosting provider. This error means something on your server prevents your site from connecting to social network’s API. It could mean that DNS is broken on your server or your server disallows outgoing connections. Either way this is something your hosting provider needs to look at.
** If you are getting Permission denied error, it usually means your hosting provider is blocking access to social network or social network is blocking access from your hosting provider.
*** If you are getting Failed to connect to 2a03:2880:2110:9f01:face:b00c:0:4: Network is unreachable – 2a03:2880:2110:9f01:face:b00c:0:4 is IPV6 address. IPv6 is a new Internet Protocol standard. This error means that IPv6 is activated, but it is not correctly configured on your server. You need to contact your hosting provider about that.
**** Suggested solution for “Operation timed out after …” from one of our users:
The solution was adding the following filter to my themes’ functions.php file, allowing the user to change the timeout to whatever they need to, in order to accommodate SNAP.
add_filter(‘http_request_timeout’, function(){return 5;});
Update. (Answer to the most popular reply to this FAQ which is “My Hosting provider says that everything is fine, so fix your plugin”):
Let us explain how it works.
Plugin does not connect to Facebook by itself. It asks WordPress to do it by calling standard WordPress function wp_remote_get().
WordPress also does not connect to Facebook by itself when asked. It asks PHP to do it by calling standard php curl_exec() function.
PHP also does not connect to Facebook by itself when asked. It asks the system binary library that installed on the server and called “cURL” to do it.
That library connects to Facebook. That library generates “Failed to connect to .. (or any other from the list above)” error and passes it to PHP that passes it to WordPress that passes it to the plugin.
Only your hosting provider could answer why that system binary library generates that error and do something about that.
* Error:(#368) The action attempted has been deemed abusive or is otherwise disallowed
* Error - You have been temporarily blocked from performing this action
* [ERROR] You can’t post this because it has a blocked link. The content you’re trying to share includes a link that’s been blocked for being spammy or unsafe
* [ERROR] Your message couldn't be sent because it includes content that other people on Facebook have reported as abusive.
* [ERROR] This message contains content that has been blocked by our security systems.
* [ERROR] The content you’re trying to share includes a suspicious URL. Please remove this link to continue.
* [ERROR] A Link in Your Post Might Be Unsafe.
* [ERROR] Sorry! We blocked this link because it may lead to spam.
* [ERROR] Sorry! Activate an exclusion that we use to combat spam
Basically this means that network does not like your posts.
- In some cases network does not allow posts from your website/domain/server/IP/etc. (For example the whole 000webhost.com free hosting provider is permanently banned on Facebook and some other networks. Too many people tried to setup the sites there for the purpose of spam.)
- In some cases network rejects the content of your posts or links from your posts. Many networks do not allow some or all URL shorteners.
- In some cases network does not like how often you make your posts. Please do not post too much or too often. Please follow the terms and guidelines for each network.
- Some networks don’t like shortened URLs. Please make sure you are not using URL shortener.
Please contact network directly if you have questions or concerns about that issue. If you get problems with Faceboook you can also try to check your site in the “Facebook Debug Tool”: https://developers.facebook.com/tools/debug
Such silent error usually a sign of the broken content filters. Content filters are applied to the post text before displaying it. They used by WordPress and third party plugins to beautify and process some formatting tags like shortcodes. Some incorrectly written plugins assume that content filters are applicable only for displaying post so they simply kill execution if applied for any other reasons (like preparing the text for autoposting)
Please go to the plugin settings, scroll to the Debug/Report Settings and check the checkbox titled “My Content Filters (apply_filters(‘the_content’) are broken, don’t use them”
Note: This will make %EXCERPT% work as %RAWEXCERPT%, %FULLTEXT% as %RAWTEXT%, etc…
I am getting: PHP Warning: xxxxxxxxx xxxxxxxxxx xxxxxx
I am getting: Deprecated: xxxxxxxxx xxxxxxxxxx xxxxxx
How to fix it?
PHP Notices and PHP Warnings are harmless. They are not errors, they are just a messages to developers informing them about some things that might require attention. Since Notices and Warnings are not errors, they do not require immediate fixes or solutions. Only developers should see them. If you are are seeing notices and warnings, it means that your server is in DEBUG mode. You don’t need DEBUG mode if you are not a developer, so please take your site out of it. There are many ways to activate DEBUG mode, so please turn it off the same way you turned it “on” or consult your server admin if you don’t know how to do it.
PS: Yes of course we are paying attention to all Notices and Warnings and making all necessary fixes or changes. We just mean that notice or warnings does not require an immediate fix. Please put your site in regular non-DEBUG mode, so you won’t see them.
Are you sure you are using WordPress built in “Schedule” functionality and not some third party plugin or service to schedule your posts? Some plugins like “Publish to Schedule” are not compatible with SNAP.
Our plugin posts to all configured social networks at the time post goes live. Technically speaking our plugin is hooked to the event of changing post status from whatever to “Published”. This event is triggered when you hit “Publish” button, when you post on your site from email, when you publish post from your iOS/Android Device, when external plugin correctly published new post, and when scheduled post becomes live. Some third party plugins (like “Publish to Schedule”) change the status of the post to “Published” right when you create it and then just keep it hidden until it’t time to present it. SNAP reacts on the change of the status and autoposts it. Some other third party plugin make post “Published” for several seconds for some internal reasons and then revert it back to “Scheduled”. Again SNAP reacts on the change of the status and autoposts it. Please use built in “Schedule” functionality from WordPress or any third party plugin or service that changes post status correctly.
Some networks (Instagram, VK, etc..) require the actual image file to be uploaded. If plugin can’t read the local file it must grab it and save it in the temporary folder before uploading.
Plugin asks the server system to get it the writable temporary file by calling standard PHP function “tmpfile()” (http://php.net/manual/en/function.tmpfile.php). This function suppose to make writable file in your system defined temporary folder.
If tmpfile returns wrong temporary folder or file is not writable, it means your server or PHP itself is misconfigured and your hosting company must fix that. Please contact your server admin or hosting provider and ask them why standard PHP function “tmpfile()” is not working on your server.
Facebook “Business” or “Advertising” accounts can’t manage apps. This is an unavoidable Facebook limitation. Only real user accounts are able to create and manage apps.
Please login to Facebook as a personal account to be able to create app. Then setup this app in the plugin. Then you have two options:
1. You can add your personal Facebook account as “Administrator” to your page. Don’t worry, all posts will be made as your “Business” name, not from your personal account. Association of your personal account with that business page won’t be seen by anyone other then you.
2. Logout from Facebook as personal account, login as your Facebook business account, then to to the plugin Facebook settings and authorize the app as business account.
The reason for “An unknown error has occurred” error is broken/corrupted image.
Please check that your image is ok, has absolute path, and please make sure that your server doesn’t have some king of protection against direct downloads of your images (hotlinking protection).You can check your images using Facebook Debugger Tool – https://developers.facebook.com/tools/debugThen just enter the URL of your image to the field, click “Debug” and see the error.
Twitter throws “Error creating status” for the exact same reason.
UPD: Sometimes Facebook throws this error when it’s servers overloaded or their image cache is corrupted. The thing to do in that case is to wait couple days till they fix it on their side.
Several reasons could be responsible for this. It could be your default privacy settings, your app could be “Sandboxed”, your posts could have low priority, etc..
First of all check if your app is not “sandboxed”:
Facebook->Developers->Apps->Your App Settings->Click “Status & Review” on the left. Change “Do you want to make this app and all its live features available to the general public?” switch from “No” to “Yes”.
Then check “Permissions”. “Default Activity Privacy” may be set to “Only Me”, must be “Public”
Then check “Advanced”. Some different settings here also could filter out your posts.
If none of that helps you can try to create a new Facebook app with all default settings and use it.
If you are seeing the post and it’s public, but still getting 0 views, most probably you are making an “Attached” post, but expecting the results as from “Shared” post. “Attached” posts are not included in the statistics. Please see the difference between Facebook post types.
This message means your plugin either not authorized or lost the authorization. Please click “Authorize” or “Re-Authorize” link and follow the authorization wizard.
Important: When Facebook Authorization Wizard asks you for the access privileges to your profile/pages, do not uncheck anything or click “Skip”.
Facebook don’t have the ability to request permission to just one page. It’s either all of them or none. If you click “Skip” it means you forbid Facebook from posting to any of your pages, groups or profiles.
Our plugin will post only to the page that you specify on the “Your Facebook URL” field.
The most popular cause for “The user hasn’t authorized the application to perform this action” is that your domain is not configured for your app.Please read and carefully follow the installation instructions:
You missed/messed steps 1.4 and 1.5 from Facebook section:
4. Click “Website”, enter your website URL
5. Enter your domain to the App Domain. Domain should be the same domain from URL that you have entered to the “Website” during the step 4.
Your Facebook app is misconfigured.
* Can't Load URL: The domain of this URL isn't included in the app's domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings.
* Given URL is not allowed by the Application configuration. One or more of the given URLs is not allowed by the App’s settings
* Given URL is not permitted by the application configuration
* Completely BLANK page right after you click “Authorize account”
* API Error Code: 191 | API Error Description: The specified URL is not owned by the application
* Invalid redirect_uri: Given URL is not allowed by the Application configuration.
This error means that URL and Domain in your Faecbook App don’t match your actual URL.it is very important that URL and domain in your Facebook App match your WP-Admin URL and domain. You must enter the URL and domain that you see in your WordPress Admin Panel. For example even if your visitors come to your blog at http://blog.nextscripts.com, but you manage your blog from http://www.nextscripts.com/blog/wp-admin/ – you must enter http://www.nextscripts.com/blog to the URL Field and www.nextscripts.com as the domain. Also please note that Facebook distinguish www. and non-www versions, so from Facebooks point of view nextscripts.com and www.nextscripts.com are two different domains.For your convinience, plugin shows your URL and Domain at the Facebook settings section.
Facebook Interface (Please see Facebook Interface instructions Step #3):
There is a field called “Attachment Text Format” in Facebook settings
Select “Set your own” in the “What should fill attachment info” section and put %RAWEXCERPT% in the “Attachment Text Format” field.
The same solution goes the LinkedIn, VK.com and other networks that support posts with attached links.
* ERROR:Error validating access token
* Session has expired at unix time XXXXXXXXXXXXX
* Expired access token. Timestamp: XXXXXXXXXXXXX
* Invalid or expired token
* Posts where the actor is a page cannot also include a target_id
* The ‘xxxxx_xxxxxx’ permission must be granted before xxxxxx xxxxxx.
* Error validating access token: The session has been invalidated because the user has changed the password.
* Error validating access token: Session does not match current stored session.
* The token used in the OAuth request is not valid.
* 401 – Not Authorized
* (#200) Permissions error
* Invalid appsecret_proof provided
* [Error] => No Auth Token Found
Facebook issues its tokens for 30 days. Each autopost renews the token. This message means that you either haven’t posted to Facebook for 30 days or Facebook has your token invalidated for some internal reasons. When you changed the Facebook password session has become invalidated as well.
The solution is the same, please to to the plugin Facebook settings and click “Re-Authorize this Facebook Account” link.
Other networks also have some expiration rules for tokens. Solution is the same – click “Re-Authorize this XXXXXXX Account” link.
Solution:
This actually has nothing to do with the plugin. This is the setting of your page. Please go to your Facebook Page, click “Edit Page”->”Update Info”, click “Your settings” from the left menu -> Posting Preferences, check checkbox “Always comment and post on your page as [Page Name], even when using Facebook as [Your name].”
UPDATE: (Sept, 2013) It looks like for some users Facebook has removed “Always comment and post on your page as [Page Name], even when using Facebook as [Your name].” checkbox from the settings and left users hanging at some uncertainty. We are currently investigating this issue and trying to find out the way to specify what account should be used for posting.
UPDATE: (Dec, 2013) The person who authorizes the plugin must be an admin of the page at the authorization time. Post will appear as page name in this case. If this doesn’t work, try to re-authorize or create a new Facebook app.
If you choose Link attachment type: Share a link to your blogpost then from Facebook’s point of view you are sharing the link. It means that your content MUST have one link. Just one and only one.If you got this error then your content has more then one link and Facebook got confused which link you want to share. Please make sure that you don’t have any links in the post text or you don’t use %SURL% in the message format. If you need more then one URL in your post then switch Link attachment type to Attach your blogpost
Your Facebook is already auto-posting to Twitter. When it sees the same tweet made by our plugin it fails with this error. You need to either unlink your Facebook from Twitter or disable Twitter auto-posting from our plugin.
If you decide to unlink your Facebook from Twitter:
Go to http://www.facebook.com/twitter and remove the link to twitter from the affected wall (Click on “Unlink from Twitter”).
* [ERROR] (#1500) The url you supplied is invalid.
* [ERROR] An unexpected error has occurred. Please retry your request later.
* [ERROR] This link could not be posted.
My URL is valid. Do you have any idea what this problem is about?
Please see this thread about error #1500:
http://wordpress.org/support/topic/error-1500-the-url-you-supplied-is-invalid
Quick summary: When you submit new link to Facebook, Facebook takes a look at this link and indexes it. When Facebook servers are overloaded they can’t index it during the request time. Facebook throws one of the errors mentioned above. Facebook still indexes the link, so the second try couple minutes later usually goes without any problems.
#1500 Error was very common during summer 2013, then it become better. Recently (Jan-Feb 2014) the same problem resurfaced as “An unexpected error has occurred” or “This link could not be posted” error.
Yes we do have a pretty good idea what this problem is about, but we can’t do anything with this. This problem is on Facebook side and they need to fix it. The problem is that Facebook servers are overloaded and if your site is not fast enough for them to get all necessary info in time, so they just trow it with #1500 error. They need to upgrade their infrastructure and increase the timeout. Until that you can only try to set the correct OG: tags, speed up your site somehow or find a faster hosting.
Update Jan/Feb 2014: – It looks like “Attached” posts are more likely to be affected by this then “Shared”, so try to switch the format.
Staring from SNAP version 3 Facebook settings have a new option “Let Facebook fill the link info”.
If this option is selected it’s basically means that plugin just does NOTHING. It just tells the the Facebook – “Here is the URL to share – do whatever you like with it”. There is noting else. Nothing could be broken, nothing for us to fix. Whatever happens on Facebook pages and how it’s shown there is totally up to Facebook. SNAP plugin just not involved at all.
Facebook will decide what image, title and description to take by itself and ignore all plugin settings. Facebook takes this info from og: metatags, so if you like to define what info will be shown make sure that those metatags are configured on your site.
Facebook introduced API 2.0 on April 30, 2014 and forced all users to move to it. it brought some changes to the requirements for app and page ownership.
This means that the Facebook app, Facebook profile or page and the user who authorizes the app MUST belong to the same Facebook account. This Facebook account MUST be an admin for the page or member of the group where you are going to autopost.
Please see the full history of the issue here: http://www.nextscripts.com/known-issues/facebook-issues/
* (#200) Posts where the actor is a page cannot also include a target_id
* (#200) The target user has not authorized this action
* (#803) Cannot query users by their username
* Reported Error: Unsupported get request.
* No errors, but posts go to the page with the same name, not to the group.
It’s a known bug in Facebook API that breaks posting to groups using non-numeric names.
There is a simple workaround for it.
Please use the numeric URL of your group in the plugin settings, http://www.facebook.com/groups/{group_id}/
You can find your Group Id in your source of your Facebook Group page by searching for group_id=
You will need to Re-Authorize your account after you update the URL.
Facebook used to allow to attach playable videos to your posts. Facebook recently removed that ability. You can’t publish playable video along with the link to your site anymore. You can only post video with the link to youtube page and it will be payable.
Here is how to post with different URL:
http://www.nextscripts.com/snap-features/using-custom-urls-in-autoposts/
PS: Facebook made the change silently without any explanation or alternatives. We have no idea why or when (if?) that will be back.
How can post bigger title?
Can I make some of my text bold?
I don't like those ugly links! I want nice clickable text
Any kind of text manipulation not possible on Facebook.
* Facebook does not allow any kind of text decoration (bold, italic, colors)
* Facebook does not allow any HTML and/or text formatting (different fonts, different size of the text, images in the middle of the text)
* Facebook does not allow titled links. (i.e you can’t make words “SNAP is Here” clickable). You can only post bare links that will become clickable.
All possible variations of Facebook posts are described here: http://www.nextscripts.com/snap-features/facebook-post-types/
SNAP can post to Facebook Profiles, Facebook Pages and Facebook Groups.
You must be an owner of profile to post there.
You must be an admin of the page to post there.
You must be at least a member of the public group to post there.
You must be an admin of the closed or secret group to post there.
It’s complicated. Official Facebook API rules are:
Regular Facebook API allowed to post:
1. Facebook Profile.
2. Facebook Pages (all kinds) (User who authorized the plugin must be an admin of the page).
3. Public Groups (User who authorized the plugin must be at least a member of the public group).
4. Closed groups (User who authorized the plugin must be an admin of the closed group).
5. Secret groups (User who authorized the plugin must be an admin of the secret group).
However, there is an unofficial workaround. Facebook issued several special apps with extended permissions that can post to closed/secret groups if user who authorized it is just a member. You can authorize such app and get an auth token. This token will allow you to post to any closed/secret group where you just a member. You can enter this third party token in the “Advanced Tab”
How to get a token and configure it.
1. Find the app and it’s ID. (Please do not ask us where to find the app. We are not allowed to share that info.)
2. Visit this URL (replace XXXXXXXXXXXXXXXXXXXX with actual App ID):
https://www.facebook.com/v1.0/dialog/oauth?redirect_uri=fbconnect%3A%2F%2Fsuccess&scope=email%2Cpublish_actions%2Cuser_about_me%2Cuser_activities%2Cuser_events%2Cuser_groups%2Cuser_likes%2Cuser_photos%2Cuser_status%2Cuser_subscriptions%2Cuser_videos%2Cuser_website%2Cfriends_about_me%2Cfriends_activities%2Cfriends_groups%2Cfriends_status%2Ccreate_event%2Ccreate_note%2Cexport_stream%2Cmanage_pages%2Cphoto_upload%2Cpublish_stream%2Cread_stream%2Cshare_item%2Cstatus_update%2Cvideo_upload%2Cxmpp_login&response_type=token&_rdr&client_id=XXXXXXXXXXXXXXXXXXXX
3. You will get the standard Facebook authorization dialog, answer “yes” to everything. You end up on the blank page.
4. Visit this URL (replace XXXXXXXXXXXXXXXXXXXX with actual App ID): https://developers.facebook.com/tools/debug/accesstoken/?app_id=XXXXXXXXXXXXXXXXXXXX
5. Add new “Facebook” account to SNAP, enter anything to key and secret, click “Add Account”, open it’s settings, copy-paste that token to Advanced tab -> Auth token.
6. Enter numeric groups ID to the “Where to post” field.
It posts to the group as me, how to change that?
This is not something we can change. Those are Facebook rules, terms, and conditions. The plugin will use the name of the user who authorized the Facebook app.
1. Post to user profile will be posted as the user’s name.
2. Post to all kinds of pages (business, fan, etc..) will be posted as page’s name.
2. Post to groups will be posted as the user’s name. (!) There is no such thing on Facebook as post as “Group’s name”. No one can post like this.
- I am getting "suspicious activity" emails from Google showing logins from some weird location! Why is that?
- Your Google+ account is locked for the new applications to connect.
****This is applicable to Blogger and Youtube as well
In order to post to Google+ Plugin need to logon to your Google account from your server. If your server is located far from your usual login place (home area), Google may try to protect you and block that login asking you for confirmation. You may receive “suspicious activity” email and ” Your Google+ account is locked for the new applications to connect” messages.
You need to tell Google that you allow your server to login on your behalf.
Here is what you need to do:
[Important Note] You need to do this from the same account you use in the plugin/api. If you are currently logged in more then one Google account, logout from all of them, login with the correct one, and then do the following:
1. Setup your Google+ account in the plugin or API.
1. Temporary Unlock your Google account for new applications to connect:
– Logout from ALL Google sessions
– Go to https://accounts.google.com from your browser and login to your Google+ account that you will be using with SNAP.
– Visit https://accounts.google.com/UnlockCaptcha page
– You will get a message “Allow a new application to access your account”. You will see:
– Click “Continue” – you will see “Account access enabled” message.
2. Go to your WP Admin Panel->Settings->Social Networks AutoPoster->Google+ Settings.
3. Click “Submit Test Post to Google+” button.
Update: One more thing. This is applicable ONLY to the Blogger in the “Free” Plugin version.
Log in and go to https://www.google.com/settings/security
Under Account permissions enable Access for less secure apps
Again. Only free blogger API in the free plugin is “less secure”. You don’t need this for Goolge+, Youtube or Blogger “Pro”.
Google+ uses the “Open Graph” tags to get the thumbnail image, title and description of your post: http://ogp.me/
You need to setup a special meta tags, defining what image, title and description should be used,
for example: <meta property=”og:image” content=”http://url.of.your.image.jpg” />SNAP for WordPress plugin has built-in support for OG: meta tags: Plugin Settings->Other settings->”Open Graph” Tags-> Add Open Graph Tags It’s very basic, but it should work. There are several plugins specifically for OG: tags and almost all top WordPress SEO plugins have ability to add them.
Google set a limit of images you can upload to Google+. You reached that limit. Please delete some images from default album or move them to another album.
1. Please login to your account manually and make sure your Google+ service is not interrupted by some “Updated Privacy Statement” that you need to agree with before you can post.
2. please make sure you don’t have “2 Step Authentication” enabled.
3. Please try FAQ #3.1
In order to post to Instagram plugin need to logon to your Instagram account from your server. If your server is located far from your usual login place (home area), Instagram may try to protect you and block that login asking you for confirmation. You may receive “suspicious activity” email or message and you might be asked to confirm new login by solving captcha or clicking “Confirm” button.
Please open instagram app on your phone, login with the same account and confirm your new login by either resetting your password, solving captcha or just clicking “Confirm”. It will work fine after that.
Possible solutions:
1. Your image is not ok. Please make sure your posts have images and those images are not broken or corrupted, not protected by some “hot-linking” protection service and valid for Instagram posting. (I.e. not animated gifs, broken, or some weird formats like .bmp, .eps or .tif
Also Instagram can throw this error if your image size/dimensions/ratio is not acceptable. This is especially the case if you chose not to crop your images by the plugin.
2. You have HTML in the message format. Please post only plain text. HTML can come from tags like %RAWTEXT% or %FULLTEXT%.
3. Sometimes this helps. Open Instagram app on your phone, logout and log back in.
Sorry to say, but you hit the Instagram’s SPAM filter.
Please see the part of instructions the we really recommend to read before posting.
http://www.nextscripts.com/instructions/instagram-auto-poster-setup-installation/#spam
Instagram will unmark your account as “Spammer” after some time, meanwhile please try to make several posts from your phone without any links or hashtags.
Plugin does not control images for LinkedIn. LinkedIn does that by itself using your OG: tags and other info. Please make sure your OG tags are set correctly.You can check the requirements for LinkedIn images (and other OG: tags) here: https://developer.linkedin.com/documents/setting-display-tags-shares
Broken reCAPTCHA image is a sign of broken/misconfigured CurlSSL. Please check and make sure your curl can open https websites. Please go to the Help/Support tab and click “Check SSL” to see the https problems.
Most probably someone who uses the same hosting company was abusing LinkedIn. As the result, LinkedIn blacklisted your hosting company’s whole IP range.
Please just follow instructions from the message and it will work.
There are only two ways to solve this.
1. Please find a working proxy server and test it in your browser. Login to LinkedIn from your browser configured with proxy and make sure you get to your account. Please solve all captchas and/or enter all codes from SMS and/or email.
Enter the same proxy to the plugin. Submit the test post and plugin will get all necessary saved login info.
Remove the proxy and send another test. Plugin will login to LinkedIn with saved info and LinkedIn will mark your server IP as “Safe to login to that account”.
It will work fine after that.
You can find option “Proxy Settings” in the “Advanced” tab. Please use format “IP:Port” and “Username:Password”.
2. You can use the hosting company who’s clients haven’t tried to abuse LinkedIn previously and who’s IPs are not banned there.
Pinterest uses this error when it doesn’t like the content that you are trying to submit or when something is down/broken on Pinterest.com.Please check that your image URL and link URL are correct and valid.
Please make sure that your image does not contain adult, abusive or any other disallowed on Pinterest.com content.
Please make sure that your image description does not contain adult, abusive or any other disallowed on Pinterest.com content and your description does not appear as spam.
We really can’t know why Pinterest doesn’t like your content, there is not further info available.
Basically this means that Pinterest does not like links in your posts or links to your posts. In most cases Pinterest just does not allow posts with links to your website/domain/server/IP/etc.. In some cases Pinterest rejects the content of your posts.
For example links to any site hosted with 000webhost.com free hosting provider are permanently banned on Pinterest, Facebook and Twitter. Too many people tried to setup the sites there for the purpose of spam.
Also Pinterest does not allow any kind of URL shorteners, so please make sure you don’t use %SURL% or another kind of shortened URLs in your post.
Please contact Pinterest directly if you have questions or concerns about that issue.
Pinterest is slow. It’s slow in general. It takes quite some time for it to return the requested info. Most probably your server has a very short timeout that is not enough for Pinterest.
Our script is trying to increase timeout setting for all calls to Pinterest. Most probably your server is set to ignore such things. Please increase timeout.
This message means that Pinterest can’t get your image. Pinterest is an image sharing network. You must supply a valid image URL along with your post. You can’t post there without an image. Please make sure it’s available at the time of post. Please turn off any kind of “hotlinking protection”. You can also try to set a delay in case your image is not ready yet at the moment post goes published.
Pinterest has your Hosting IP in the list of potentially suspicious networks and blocked it. This means your hosting provider was recently used to abuse Pinterest.
This usually happens when:
– You use some “cloud cdn” providers like CloudFlare or Incapsula.
– You are on shared hosting and one of your neighbours was/is abusing Pinterest.
– You are hosted on some “activity friendly” providers like Amazon AWS, LeaseWeb, OVH, RedStation, ServerCentral, SoftLayer, etc.
1. Try to contact Pinterest and ask them to unblock your IP.
All you need to do is to fill one form on help.pinterest.com/en/contact
1. Choose “Getting into my account”, then “Get out of safe mode”, then click “I still need help”
2. Fill your issue info with your website IP and say “I am not running any bots, please allow me to use my account”.
2. If you are using CloudFlare or one of the permanently blocked providers you can use proxy. (You can configure it in the “Advance tab”)
Do you actually have any subreddits that you own? Not the subreddits you subscribed to, but subreddits you have created or at least have rights to moderate?
Reddit allows you to post ONLY to the subreddits made or moderated by you. All posts to other subreddits are considered “SPAM” and will lead to the suspension of your reddit account.
Reddit has some pre-qualifications (like certain amount of karma) before you can freely post and you need to meet those pre-qualifications. Yes, you need it even for your own subreddit . This is Reddit’s policy, nothing can be done about that.
http://www.scoop.it/u/username is your user(profile) URL. Scoop.It does not allow any postings to be made to user URLs, you can only post to “Topics”.
Please check your account, you have topics (like http://www.scoop.it/t/topic-name), so you need to enter topic-name to this field.
Please check what do you have in the “Post Text Format” field in plugin’s Tumblr settings. Your first image could come from “Image Post”, second image could come from %IMG% tag and your third image could come from %FULLTEXT% tag.
Please see here for more info about formatting tags:
http://www.nextscripts.com/snap-features/message-formatting-tags/
Answer: You just need to follow the instructions step by step. Please don’t skip anything.
Please see #4 and #5 for Twitter:
4. Click “Permissions” tab. Change Access level from “Read Only” to “Read and Write“. Click “Update Settings”.
5. Click “Keys and Access Tokens” tab. Scroll to the “Your access token” and click “Create my access token” button. Refresh page and notice “Access token” and “Access token secret”. Make sure you have “Read and Write” access level.
Basically this means that Twitter does not like links in your posts. In most cases Twitter just does not allow posts with links to your website/domain/server/IP/etc.. In some cases Twitter rejects the content of your posts.
For example links to any site hosted with 000webhost.com free hosting provider are permanently banned on Facebook and Twitter. Too many people tried to setup the sites there for the purpose of spam.
Please contact Twitter directly if you have questions or concerns about that issue.
This message is coming from the new Twitter’s spam protection mechanism. It’s analyzed your message and marked it as spam. As you can expect they don’t share any information about how this thing works. Try to change the format of your messages and use/don’t use/change URL shortener. There are also some reports that Twitter rejects posts coming from hosting providers that were used to abuse it.
Please note: Despite the fact that error is saying “might be automated”, it doesn’t mean that Twitter rejects the post because it was made though the API. “Automated” there doesn’t mean “posted/submitted automatically”, it means “written/generated automatically”.
Please make sure that all your info such as URL, keys and secrets are in the right places and belong to the same account. This could be the only reason for this error.
Just follow our instructions step by step: http://www.nextscripts.com/setup-installation-twitter-social-networks-auto-poster-wordpress/
It’s not that simple. Actually such counter is impossible to implement. Some of the tags could be processed only after you publish the post which makes it impossible to count characters at the time of writing.
Please see here for the very detailed explanation: Why we don’t have a Twitter characters counter
