Help, Support & Customization for
Twitter Tools
Call now: 720-288-0398
Using WordPress HelpCenter for help with Twitter Tools supports Alex King (the plugin developer).
You can choose your own application name so long as it is unique, not “Web,” “Twitter Tools,” etc.
The application name shows up in streams for users on Twitter.com. For instance if you look at our Twitter stream – http://twitter.com/wphelpcenter – under each tweet in light gray text you will see, “via CoTweet”. This is because we use an application called CoTweet to send our Tweets.
The value you provide here is what will show up in that spot. Perhaps using the domain name of your site or the name of your site is a good option. It is up to you what you enter here. Please note that you must choose a name that is not in use by any other application/user. It must be unique. #
The link for “My Access Token” is located in the right hand column of the page that contains your consumer key and secret on dev.twitter.com. It’s just below the “Reset Consumer Key and Secrete” button and right above the “View Your Applications” button. See this screen shot for details. #
You will need information from two pages to get Twitter Tools set up. If you’re not able to connect to Twitter, it may be that something went wrong with your copy and paste of the appropriate API keys and tokens.
You’ll get the Consumer Key and Consumer Secret from this page — http://dev.twitter.com/apps/######/
You’ll get the Access Token and Access Token Secret from this page — http://dev.twitter.com/apps/######/my_token
If you’re logged out of Twitter’s Developer Area, you can log in at http://dev.twitter.com/login. Once you’ve logged in, you can click Your Apps at the top of the page to get to your Twitter Tools app. #
If you are receiving this error is likely because your web host is serving your files using PHP version 4. However, many web hosts are able to support PHP version 5 via configuration options. Try contacting your web host and see if they are able to switch your account to make use of PHP version 5 or instruct you on how to make the switch yourself. #
Please check with your web host to ensure they have the PHP CURL libraries installed as they are required for Twitter Tools to function. CURL is helpful to many web applications and once installed, this error message or any others mentioning CURL should stop displaying. #
This problem typically has to do with your hosting environment. There is a PECL module that includes OAuth support for PHP. It is loaded on some Web servers, and by default it does not have the class OAuthSignatureMethod_HMAC_SHA1 defined. Twitter Tools attempts to define this class, but the incomplete PECL module prevents Twitter Tools from loading it’s complete version of the module. Please contact your Web host to see if they can disable this module for your site. #
Getting a blank page when attempting to connect to Twitter is usually a result of your Web host serving your site with an older version of PHP or not having the cURL extension compiled into PHP. Please see the related FAQ entries on this page for more information. You will want to contact your host to see if this is an issue and see if they can resolve this problem for you. #
Twitter limits tweets to 140 characters. Twitter Tools has to allow for the length of the shortened URL to your post, plus the length of the prefix, when determining whether the post title will have to be truncated. Longer post titles will be truncated because of Twitter’s limitation. #
Most likely you have enabled the optional bit.ly plugin, but have not entered a valid API key and password. A common error is copying and pasting an extra space along with the bit.ly API key – make sure only your API key and no spaces are included in that field. #
On the Twitter Tools settings page, try using the Reset Tweet Checking and Update Tweets buttons. #
You may want to double-check that your server time is correct. OAuth requires that your server time is consistent with the server time on Twitter’s side. Fixing this issue has helped get the plugin working for a number of users. #
For performance reasons, and to avoid exceeding Twitters connection limits, Twitter Tools stores all tweets in a table on your WordPress installs database. Any tweet’s retrieved from Twitter will remain in your sidebar widget until they are “pushed off” by new Tweets #
If your server had a hiccup in the middle of posting a digest, Twitter Tools might think that it’s still trying to post a digest and thus won’t start working on another. Try clicking the ‘Reset Digests’ button on the settings page – that may get things working again. #
Anyone who has a 'publish_post' permission. Basically, if you can post to the blog, you can also post to Twitter (using the account info in the Twitter Tools configuration).
Actually, Twitter Tools has taken this into account and you can safely enable both creating posts from your tweets and tweets from your posts without duplicating them in either place.
No, Twitter Tools sends your long URL to Twitter and Twitter chooses to shorten it or not.
As of version 2.0 a plugin to do this with the Bit.ly service is included as an option.
Yes, Twitter Tools includes a filter:
tweet_blog_post_url
as of version 1.6. Plugins for this filter may already exist, or you can create your own. The plugin needs to attach to this filter using the standard WordPress add_filter() function and return a URL that will then be passed with your blog post tweet.
As of version 2.0 a plugin to do this with the Bit.ly service is included as an option.
Yes, as of version 2.0 you can change this on the Options page.
No, this is not a good idea. Twitter Tools needs to be able to look at the beginning of the tweet and identify if it's a notification from your blog or not. Otherwise, Twitter Tools and Twitter could keep passing the blog posts and resulting tweets back and forth resulting in the 'spinning fireball of death' mentioned above.
json_encode() function, required by the changes in WordPress 2.9 (version 2.1) created a problem for users with servers running 32-bit PHP. the json_decode() function treats the tweet ID field as an integer instead of a string, which causes the issues. Thanks to Joe Tortuga and Ciaran Walsh for sending in the fix.Bit.ly plugin
Exclude Category plugin
Hashtags plugin
Using WordPress HelpCenter for help with Twitter Tools supports Alex King (the plugin developer).