Support FAQ

When I follow the instructions to allow your plugin authorize/access to my Facebook/Twitter/Tumblr/LinkedIn/ScoopIt/etc.. account, it redirects me to the “Blank” page, “You do not have sufficient permissions to access this page” message, “Google Analytics for WordPress Configuration” page, “woocommerce page setup”, or some other plugin” page.

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”, “WooCommerce Piwik”, “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.

1.2. I am getting duplicates! What should I do to prevent it?

I am getting duplicates! What should I do to prevent it?

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

1.3. How to change default message format?

I changed the default message format to “%TITLE% – was published on %SITENAME% – %URL%”. It still publishes my posts as “New post (%TITLE) has been published on %SITENAME” Can you please tell why is that?

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.

1.4. Image Errors: “Could not get image”, “Server can’t access it’s own images”, “Error uploading photo” etc..

I am getting this error: “Could not get image, will post without it – Error” or “Server can’t access it’s own images. Most probably it’s a DNS problem.” or “(Tumblr) 400 – Bad Request – [0] => Error uploading photo”

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 https://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

1.5. Wrong or missing image.

Posts made by the plugin don´t show the image from the post. They show no image, website logo or some random picture.

Answer got to big for the FAQ, so please see the full article How the plugin gets/sets the images and why they could be wrong or missing

Also please note that Facebook recently changed it’s policy regarding the info (including the image) of shared links. Known Issues: Incorrect Shared Links Info (Image, Title, Description)

1.6. Not Enough Memory allowed for PHP

I am getting this error “Not Enough Memory allowed for PHP. You have 32 MB. You need at least 64MB”

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.

1.7. [Skipped]- User ID XXX can’t autopost – Post ID:(XXXXX)

[Skipped]- User ID XXX can’t autopost – Post ID:(XXXXX)

Please see here for explanation and resolution of this: New Security Rules starting with version 2.7.13

1.8. error:0D0890A1:asn1 encoding routines:ASN1_verify:unknown message digest algorithm

I am getting this error "error:0D0890A1:asn1 encoding routines:ASN1_verify:unknown message digest algorithm"

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.

1.9. SSL/https/certificate related issues

Facebook (Twitter, LinkedIn, Delicious, Pinterest, etc..) is giving one of the following errors

* 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.

This error means that cURL is misconfigured on your server. Most probably curl ssl(or openSSL lib) is broken or it simply can’t find the certificates at the pointed location.Please contact your hosting provider and ask them to turn on or FIX “client side SSL” for your site.

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: https://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: https://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

1.10. Connection errors like “Couldn’t connect to host”, “Couldn’t resolve host”, “connect() timed out”, “Failed to connect to …”, etc…

I am getting one of those errors when I try to authorize my Facebook (Blogger, Google+, Pinterest, Twitter, etc..) account:

* [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.

1.11. SPAM/unsafe/abusive/suspicious content errors like “The action attempted has been deemed abusive or is otherwise disallowed”

When I publish a new post to I am getting one of those errors:
* 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

1.12. Nothing is posted and nothing in the log.

I click "Repost" button, message says "Posted", but nothing on my account and nothing in the log.

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…

1.13. PHP Notice and PHP Warning

I am getting: PHP Notice: xxxxxxxxx xxxxxxxxxx xxxxxx
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.

1.14. Scheduled Posts are getting published immediately.

Scheduled Posts are getting published immediately.

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.

1.15. Your temporary folder or file is not writable

Your temporary folder or file is not writable

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()” (https://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.

1.16. What is “URL of your SNAP Plugin “Accounts” page” and how to find it?

What is “URL of your SNAP Plugin “Accounts” page” and how to find it?

Please go to your WP Admin panel and click on “Accounts” under the SNAP|Autoposter in the left side menu. The URL of that page is the “URL of your SNAP Plugin “Accounts” page”

Facebook Common Problems

2.1. I can’t create facebook app. It redirects me back to my account.

I can’t create an app on developers.facebook.com/apps. When I am trying to enter that page it redirects me back to my account? What should I do?

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.

2.2. Facebook Error: [Error] => [ERROR] An unknown error has occurred

Twitter Error: Error creating status

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.

2.3. Only I can see the posts, nobody else can.

Another question for the same answer: Why the "Boost Post" button is disabled?

Several things 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.

2.4. ERROR:(#200) This API call requires a valid app_id or [Error] => No Auth Token Found/Not configured

I did create the developer account and got my App ID and the App Secret. I have followed all instructions but when I submit a test post to FaceBook, I get this error message: ERROR:(#200) This API call requires a valid app_id. [Error] => No Auth Token Found/Not configured

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.

2.5. Facebook Error: “The user hasn’t authorized the application to perform this action”

Facebook Error: “The user hasn’t authorized the application to perform this action”

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.

2.6. Error: No appsecret_proof parameter was specified

When try to AUTHORIZE my Facebook account I get this error message: Can’t get User. No user returned. No appsecret_proof parameter was specified

Your Facebook app is misconfigured.

2.7. Authorization errors like: “Can’t Load URL” or “Given URL is not allowed by the Application configuration”

Every time I try to AUTHORIZE my Facebook account I am getting one of those errors:

* 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 https://blog.nextscripts.com, but you manage your blog from https://www.nextscripts.com/blog/wp-admin/ – you must enter https://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.

You must have the correct domain and URL in 3(three) places in your Facebook app.

1. App Domains

2. Site URL

3. Valid OAuth redirect URIs. (Also please make sure that “Use Strict Mode for Redirect URIs” is set to “No”)

Please see Facebook Interface instructions

2.8. Wrong “attached link” or “shared link” description

When plugin auto-publishes to Facebook as an “attached link” or “shared link” post type it doesn’t include descriptions to attached post. Description shown as blank or some kind of script code or even some random info from another page.

Facebook recently changed it’s policy regarding the shared links preview info. Known Issues: Incorrect Shared Links Info (Image, Title, Description)

2.9. Token Issues like “Error validating access token”, “Session has expired”, “Expired access token”, “Not Authorized”.

I am trying to post to a Facebook (LinkedIn, Twitter, Plurk) and I get one of those error messages:
* 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.

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?:

I am posting to Facebook Page but all posts appear as my name, not as page name. Is there a way to change that?:

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.

2.11. ERROR: (#1) An error occured while creating the share

When I publish a new post to Facebook I am getting this error: [ERROR](#1) An error occured while creating the share ( spelling error in the word “occurred” comes from Facebook, so the error should be [ERROR](#1) An error occurred while creating the share)

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

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.

When I publish a new post to Facebook I am getting this weird Twitter Error: Error:(#100) The status you are trying to publish is a duplicate of, or too similar to, one that we recently posted to Twitter.

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 https://www.facebook.com/twitter and remove the link to twitter from the affected wall (Click on “Unlink from Twitter”).

2.13. [ERROR] (#1500) “The url you supplied is invalid” and [ERROR] “This link could not be posted”

When I publish a new post to Facebook I am getting one of those errors:
* [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:
https://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.

2.14. Invalid Scopes: manage_pages, publish_pages.

Invalid Scopes: manage_pages, publish_pages. This message is only shown to developers. Users of your app will ignore these permissions if present.

Since May 1st, 2018 Facebook requires all “Live” apps to be reviewed and approved for posting permissions like manage_pages, publish_pages.

You are getting this error because your app is in “Live” mode and not yet reviewed and approved.

2.15. Errors: “(#200) The user hasn’t authorized the application to perform this action” and “Can’t get Page Token. NO TOKEN RETURNED”

I am getting [Error] => (#200) The user hasn’t authorized the application to perform this action Another message of the same problem: Can’t get Page Token. NO TOKEN RETURNED.

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: https://www.nextscripts.com/known-issues/facebook-issues/

2.16. Error messages when trying to post to a Facebook group

* Reported Error: (#803) Some of the aliases you requested do not exist:
* (#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, https://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.

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.

I have a video in my post, but when I post to Facebook it’s posted as image preview and it’s not playable.

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:
https://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.

2.18. How can I change the color of my text?

How can post text followed by an image followed by more text?
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: https://www.nextscripts.com/snap-features/facebook-post-types/

2.19. Where can I post on Facebook? Should I be an admin of the page/group?

Where can I post on Facebook? Should I be an admin of the page/group?

1. With Free Native Facebook API SNAP can post to Facebook Pages and/or Facebook Groups. You must obtain explicit approvals from Facebook for posting to Pages and Groups.

2. With NextScripts Premium API 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 as “Page Name”. If you are not an admin posts will go to the “Community” section.
You must be at least a member of the public, closed or secret group group to post there. All group rules will apply. If group itself or your account is required pre-moderation, autoposts will be sent to moderation query.

2.20. Can I post to Closed/Secret Groups if I only a member (not an admin)?

Can I post to Closed/Secret Groups if I only a member (not an admin)?

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.

2.21. What name will be used on Facebook?

Will it use page name or my name when posting to the page?
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.

2.22. I got a notice about Facebook Graph API App upgrade. What should I do?

New Developer Alert for "MyAppName"
Your App, "MyAppName", is currently accessing Graph API v2.X which will reach the end of its 2-year lifetime on DAY Month, 201X

You don’t need to worry about that. Facebook has a “2 Years app retention policy”. After that your app will be automatically upgraded to the next version.
SNAP plugin has a full support for all versions of Graph API Apps from 2.0 to the latest 2.10. It adapts to the available Facebook API App version automatically.

2.23. [NextScripts API] Failed Session | Wrong Session

[NextScripts API] Failed Session | Wrong Session

This could mean:

Either user ID or session ID are not correct
You logged out from Facebook in your browser.

Please follow our instructions and get a correct, active and working session ID. Please do not logout from Facebook after that.

2.24. Your Account was accessed from unusual location / Facebook asks me to change password

Your Account was accessed from unknown location.
Your Account is Temporarily Locked
The session has been invalidated because the user changed their password or Facebook has changed the session for security reasons.
We’ve detected suspicious activity on your Facebook account and have temporarily locked it as a security precaution.
Login approvals are on.
Login checkpoint reached.

All our scripts are installed on your server and your server makes posts to your networks directly. When you make a post your server logins to your account on your behalf and makes a post. The location that Facebook is asking you to confirm is a location of your server.

Please login to Facebook from your browser and clear all obstacles (Confirm that it was you, change password, enter login code, etc..).

The further your sever from your home the more suspicious Facebook about that login. Please confirm that it was you. It might take several times and then Facebook will stop asking. Basically Facebook needs to mark your server IP as your “usual” login location. Once that happens, Facebook will stop with “suspicious activity” alerts.

Alternatively please try to use session instead of username password or vise versa.

Session Instructions: https://www.nextscripts.com/snap-nextscripts-api-for-facebook-configuration/#session

Google+ Common Problems

3.1. Google+/Blogger/Youtube – Connection Problems

- I’ve setup my Google+ page etc, but when I hit the test button I get this message “Incorrect Username/Password”, “You are not authorized to publish to this page”, “Cannot use string offset as an array” or it just stuck on “Sending update to Google+”. I am 100% sure I have correct Username and Password and I can post to that page.
- 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.

Again. Only free blogger API in the free plugin is “less secure”. You don’t need this for Goolge+, Youtube or Blogger “Pro”.

————–
Update (September 2018). UnlockCaptcha became a bit unstable. It doesn’t works for about 10% of accounts. If you are still can’t connect after unlocking please use session as described here: Use your active session ID to connect your site to Google+

3.2. Wrong image and/or description on Google+ Posts

Script is not publishing the related thumbnail with each post it sends to Google+. Google+ doesn't get the correct title and description. Where can I define them?

Google+ uses the “Open Graph” tags to get the thumbnail image, title and description of your post: https://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=”https://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.

3.3. Number of photos in album 2000 >= limit 2000

[status] => REJECTED [customerSpecificInfo] => Array ( [message] => Number of photos in album 2000 >= limit 2000 [status] => ERR_PHOTO_PER_ALBUM_LIMIT

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.

3.4. Error (NXS): Lost Login info.

Error (NXS): Lost Login info.

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

Instagram Common Problems

4.1. [message] => checkpoint_required

We detected some suspicious activity.
We need you to reset your password.

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.

4.2. Please update your Instagram app to continue posting photos

“Sorry, there was a problem with your request."

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.

4.3. It says posted successfully, but link leads to “Sorry, this page isn’t available.”

My Instagram posts are disappearing in couple minutes after I post them.

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.
https://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.

4.4. No Description – Disappearing posts – “Sorry, this page isn’t available.” and “Unknown Server Error”

“Sorry, this page isn’t available.”
“Unknown Server Error”
Post disappeared after autoposting.
Post posted without description.

If your post is posted as “Image Only” (no description) or you click the link to the new Instagram post and see this:

Sorry, this page isn’t available.
The link you followed may be broken, or the page may have been removed. Go back to Instagram.

This might happen immediately or several minutes after the post.

This behavior usually means your account is under some suspicion. Someone either reported your posts as spam or your hosting provider IP range was previously used to abuse Instagram. Please stop autoposter for couple days and post several images form your phone without any tags. This usually resolves the issue. After that please try to make posts that people won’t report as spam.

“Unknown Server Error” means that image you are uploading is already known to Instagram. It was uploaded there before and it was uploaded by some suspicious/spammy accounts. Generally it means that you are posting something that is not your new selfie. This is often combined with “Sorry, this page isn’t available” issue, but regardless, resolution is the same – login to Instagram from your phone. Post normally for several days. Your account will be restored. Review your posting strategy after that.

LinkedIn Common Problems

5.1. My shared links appear without the image. All other networks are fine, but not LinkedIn

My shared links appear without the image. All other networks are fine, but not LinkedIn

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

5.2. Broken reCAPTCHA image

I am trying to post to the company page at LinkedIn. However, I can’t get past the final setup step, which is to post a test post from the plugin. A dialog box appears in which I’m supposed to enter two words from the reCAPTCHA image, but the image isn’t show – my browser just shows an X instead of an image.

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.

5.3. Linkedin blacklisted my IP address

Linkedin blacklisted my IP address

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 Common Problems

6.1. 502 Oops! | Our server is experiencing a mild case of the hiccups

Pinterest Errors:
502 Oops! | Our server is experiencing a mild case of the hiccups. | We’ve reported it to the team. | Try again?.
Sorry! Something went wrong on our end. Please try again.

1. Pinterest uses this error when its servers are overloaded or down.
2. Pinterest uses this error when it doesn’t like the content that you are trying to submit. 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.

6.2. Pinterest Error: This pin contains a link or text that we do not allow. We have blocked this pin for your safety.

Another possible error message: Sorry, we blocked this link because it's a redirector and may lead to inappropriate content.

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 or links that redirect somewhere, so please make sure you don’t use %SURL% or another kind of shortened URLs in your post. (This especially relates to “Sorry, we blocked this link because it’s a redirector and may lead to inappropriate content.” error)

Please contact Pinterest directly if you have questions or concerns about that issue.

6.3. Error: Transfer closed with outstanding read data remaining

Error: Transfer closed with outstanding read data remaining

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.

6.4. Pinterest error: “Sorry we could not fetch the image.”

Pinterest error: Parameter 'source_url' ... is not a valid URL format.

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.

6.5. Pinterest has your Hosting IP in the list of potentially suspicious networks

Uh oh! We've found a bot
Looks like there's a bot running on your network

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”)

Reddit Common Problems

7.1. I click “retrieve your subreddits” link I am not getting any subreddit ids returned.

I click “retrieve your subreddits” link I am not getting any subreddit ids returned.

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.

7.2. ERROR: Post Rejected. Reddit thinks that you don’t have rights to post here

If I try to make a post am getting: [Error] => ERROR: Post Rejected. Reddit thinks that you don’t have rights to post here [Error] => zt565GT232hWss672kxtre94D6Da18wgr

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.

Scoop.It Common Problems

8.1. Scoop.It: I can’t set my profile URL – it’s “u” instead of “t”. and “Cannot find theme from url” error

I am trying to setup my profile, but I cannot change the first part of the URL which is “http://www.scoop.it/t/”. But my profile is “http://www.scoop.it/u/username”. It’s a "u" instead of "t". How can i change that ? Another question – same answer: I am getting the error: [error] => Cannot find theme from url

https://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 https://www.scoop.it/t/topic-name), so you need to enter topic-name to this field.

Tumblr Common Problems

9.1. Why am I getting duplicate images on Tumblr posts?

Why am I getting duplicate images on Tumblr posts? The same image is repeated three times in all my Tumblr posts. How to fix this?

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:
https://www.nextscripts.com/snap-features/message-formatting-tags/

Twitter - Common Problems

10.1. Twitter Error: Read-only application cannot POST

Twitter Error: {“error”:”Read-only application cannot POST”,”request”:”/1/statuses/update.json”} OR {“errors”:[{“message”:”Application cannot perform write actions.}]}

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.

10.2. Status contains malware

When I publish a new post to Twitter I am getting this error: “code”:188,”message”:”Status contains malware”

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.

10.3. This request looks like it might be automated

When I publish a new post to Twitter sometimes it’s ok, but sometimes I am getting this error: “code”:226,”message”:”This request looks like it might be automated. To protect our users from spam and other malicious activity, we can’t complete this action right now. Please try again later”

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”.

10.4. Twitter error: “Could not authenticate you”

Twitter error: “Could not authenticate you”

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: https://www.nextscripts.com/setup-installation-twitter-social-networks-auto-poster-wordpress/

10.5. Why there is no character counter for Twitter? Please add it, it should be easy.

Why there is no character counter for Twitter? Please add it, it should be easy.

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

Version "Pro"

11.1. Wrong Key Contact Support

Wrong Key Contact Support

1. The most common reason for the “Wrong Key” error is the outdated SNAP Helper plugin. Please make sure your SNAP Helper plugin is 1.5.5 or later. 1.4.X versions are no longer compatible with latest SNAP releases.

2. It also could be amount of memory allowed for PHP on your server. Please check and make sure it’s not 32M or less. You need at least 64M, but if you have other plugins 128M or even 256M is recommended.

3. Another possible problem is broken curl/sslcurl, please do [Test Connections and HTTPS/SSL] from Help/Support tab in the plugin and look for any possible connection errors.

SNAP Pro for Wordpress

Pro version upgrade adds the ability to configure more than one account for each social network and some additional features.

Get SNAP Pro

Latest Blogposts

Corrupted cache issue with SNAP Pro.

May 22, 2019

What happened? SNAP Pro is checking for API update every 6 hours. Today (May 22, 2019) around 6:30PM EST Google Cloud messed our update server for about 7 minutes. A bunch of "lucky" sites that were checking for update during those 7 minutes got their plugin cache...

Support for “Google My Business” is coming soon…

Oct 5, 2018

Support for "Google My Business" is coming this fall. Google recently made some kind of blog-a-like functionality available for local business listings. As a local business owner you can add posts, events, offers as well as products to your business listing. Although...

Facebook app review

Jul 6, 2018

We are getting a lot of questions about upcoming deadline for Facebook app review. People are asking what should we do. The honest answer would be: "No one has any idea". We submitted several apps for Facebook review using different ways of describing and explaining...

What happened with Facebook

May 10, 2018

What happened with Facebook? Facebook made changes to it's API access policy on May 1st, 2018. As the result we introduced our own Premium API for Facebook. We feel that we need to explain how exactly those changes affected SNAP. Since the beginning Facebook native...

Instagram issues

Dec 18, 2017

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...