Outputs tweets from any Twitter users, hashtag or keyword through the Widget interface. Can be called via shortcode or PHP function call and supports
This is determined by your settings within the widget or your custom call. The default is set to 5.
If using the update frequency "Live (uncached)" ThinkTwit will show tweets that have occurred as far back as "max days" (up to the last 7 days, due to restrictions in the Twitter API). However, any other option will utilise ThinkTwit's own cache and will therefore display anything within the cache (up to "max days"). The exception to this is when the "Paused" option is selected - this will retain tweets (and display those tweets) indefinitely (until the update frequency is changed from "Paused").
If you aren't caching tweets then a message will be shown stating: "There have been no tweets for the past 7 days", but if you are caching tweets then it will simply show the tweets stored in the cache, even if they are older than 7 days. This message can be customised within the settings.
ThinkTwit uses the widget API so should be styled correctly by your theme. It has some default CSS but you may, however, wish to turn this off (in the ThinkTwit Settings) and add your own. If so you should find the following information handy:
ol.thinkTwitTweets #tweet-nwhere n is the number of the tweet
ol.thinkTwitTweets li.thinkTwitTweet a.thinkTwitAuthor
ol.thinkTwitTweets li.thinkTwitTweet a.thinkTwitSuffix
ol.thinkTwitTweets li.thinkTwitTweet a.thinkTwitContent
ol.thinkTwitTweets li.thinkTwitTweet span.thinkTwitPublished
NOTE: Be sure to use the id to access each style in order to over-write the default CSS.
Turn on no-caching in the widget settings.
Your theme is probably not setup properly. AJAX requires a location to insert the returned data from the server-side call. ThinkTwit puts it in to the div that contains the widget. A WordPress theme written correctly should output a unique id for each widget that is output. Inform the developer of your theme to have the following (or something similar) in their register_sidebar function:
'before_widget' => '<div id="%1$s" class="widget %2$s">'
You are getting this error because the allow_url_fopen option is disabled on your server. You can resolve this by either enabling it, or if you are unable to do this (it may be a shared server) you can enable CURL in the widget options.
You may need to clear and rebuild your cache - please use the Clear Cache button within Settings -> ThinkTwit in the Admin area, and then reload the page containing ThinkTwit. Otherwise please re-install - see uninstall instructions.
You can apply a filter - see the following URL for an example:
images folder may not exist or it may not be writeable (this folder is required for caching avatars). You must create the directory if it
doesn't already exist or you must chmod it to 755 or higher so that the web server can write to the folder (depends on your web server
Once every 24 hours (assuming a request is made in this period). This value is not currently configurable.
It is likely that you have not entered your Twitter API credentials. Please see the Installation tab for more details and check your PHP error log for any errors (such as incorrect authentication or rate limiting with Twitter).
You can look in the normal error log for your PHP setup. By default this is the error_log file within the root server of your WordPress installation but this may differ for each installation so if you are unsure please ask your server administrator.
This means that you are making too many requests to Twitter. If you are not using caching you should turn this on, and if you are already using it then you should decrease the frequency that requests are made e.g. change update frequency from "Live (cached)" to "Hourly".
Live updates allow periodic updates to the user's screen every set number of seconds i.e. if this was set to 10 seconds then every 10 seconds a call would be made to ThinkTwit to request any new Tweets. To use this feature you must have no-caching turned on.
NOTE: Even though you may be have a high frequency set this does not mean you will definitely get new tweets within that frequency. This is dependent upon the frequency of updates that you have set in the update frequency for that widget, shortcode or your Output Anywhere call. If you are using caching then the call will be made to the ThinkTwit cache and not Twitter itself - it is recommended that you use caching and not live calls if using live updates or else you may find yourself blocked from Twitter.