Have finally found to add another update to ThinkTwit – it’s been just over a month since the last release as I’ve had a lot on in work. I set down today to make 3 minor changes, one of which was in the FAQ, and ended up making 7 changes in total:

• Fixed incorrect PHP function call example in FAQ
• Fixed incorrect “Show Username” type in FAQ
• Fixed incorrect boolean values in FAQ
• Removed silly copyright statement in comments
• Added link to FAQ within Plugins description to aid use of shortcode
• Fixed (intermittent) bad check of boolean for displaying avatars
• Function call and added limit to the maximum days of tweets to be output (at the request of Keith this week)

NOTE: if upgrading and already using PHP function call please add the max_days parameter after limit - parameter 5.

In addition to these changes I found two further bugs which I’ve added to the roadmap, one of which I realised I’d made a hideous oversight (passing each individual argument to the PHP function call rather than simply passing args). I’ll try to get on these a little sooner this time.

Just released a minor ThinkTwit update (1.2.1). It basically includes some pieces I wanted to include in 1.2.0 but didn’t have time, as I like to update in discrete units and to finish them before taking a break – although this break was smaller than I intended, I got a bit bored :/

It just includes some donation code, should you wish to donate to ThinkTwit’s development, and a quite useful ability to expand and contract sections of the ThinkTwit widget settings.

I’ve just released a new minor release of ThinkTwit – version 1.2.0. This release demanded a minor release (e.g. 1.x.0, rather than maintenance, e.g. 1.1.x) due to a significant re-write of the code – specifically around the visibility of functions.

The ThinkTwit class now contains all of the core functionality that operates on processing data within ThinkTwit (the tweets), especially caching and output. The only code outside of this is the Tweet class, code to register the widget, and handling of shortcodes and public function calls.

Many new features have also been introduced and there has been a major update of the readme and screenshots to reflect the changes made:

• Massive update to the readme, including updated screenshots
• Re-write of code to make better use of object orientation and private/public functions
• More flexibility in shortcodes and output anywhere function (thinktwit_output) – including ability to use caching
• Introduced ability to alter time output text e.g. “This happened 16 minutes ago”
• Added class to style error message when using AJAX
• General readability improvements to code

Hope everyone finds this useful – if you have any comments please make them below, including any requests for new features (feature list available on the ThinkTwit page).

NOTE: After updating you may need to go in to your widget settings and press Save if you find that your times (e.g. “This happened…”) do not show.

After a request from Alvin (latraverseedustick on WordPress.org) I’ve made some quick updates that allow:

• Targeting of individual tweets
• Targeting of odd/even tweets
• Targeting of author
• Targeting of author suffix e.g. ” said: “
• Linking of the avatar to the author’s profile

As per the request of Aaron Snowberger I’ve added a minor update that allows the display of the avatar of the user who posted each tweet. At the moment this just loads it live from Twitter, but I will make a future update that allows caching of this image as well for those who use the cache.

So I recently noticed that although my last update included caching, there were some times in which the cache would not be accessed correctly – specifically, when updating from Twitter it was overwriting the cache rather than updating it and then displaying the cache. This wouldn’t be a problem if the live update was full of tweets, but if it had only one it would overwrite the cache with only 1 tweet.

Additionally, have split the Live option in to “Live (uncached)” and “Live (cached)”. The former will not use the cache at all and will always go straight to Twitter (meaning if Twitter is down it will not display anything) and the latter will always check for updates from Twitter (rather than waiting x since last update to check it) and then store the updates in the cache before displaying cached tweets.

I’ve updated the ThinkTwit page on my blog with the roadmap as during this update I’ve realised a few other minor bugs. I’ll get on to these in the coming weeks.

So it’s been slightly over a year and due to various problems with my PC (an incredibly difficult issue to resolve as I had issues with more than one part) and lack of time I’ve been unable to complete the work that I started after the last update.

Anyway, I’ve finally found time and am happy to announce version 1.1.5 – it includes caching of tweets to the local WordPress database and the implementation of shortcodes. Please check the readme for more details.

I have also updated the roadmap – I will do my best to keep ThinkTwit up-to-date in the future.