ThinkTwit Update 1.1.6

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.

ThinkTwit Update 1.1.5

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.

Computer Upgraded

Well due to MSI providing me with a dud replacement motherboard I finally decided to bite the bullet and upgrade my system. I completely avoided all MSI products this time round and now my computer is running smoothly again, with some slightly faster kit.

I shall get back to ThinkTwit development and will do my best to get some updates out in the next couple of weeks.

Update

Well it’s been a while since I’ve been able to post – just thought I’d let anyone reading what’s going on and why I’ve not posted any ThinkTwit updates in a while. As you will have seen from previous posts I’ve had issues with my PC – after getting my motherboard fixed I received further issues and had to fight with MSI again to have my motherboard replaced. They eventually relented after the threat of being reported to Trading Standards and they replaced the motherboard with one that was refurbished. However, that motherboard also has an issue but that’s another story – needless to say I won’t EVER buy an MSI product again.

Since all that palava I have also bought and moved in to a new house. I’m currently without Internet and my PC is still in pieces but once I’ve got everything sorted and I’m settled (probably another month) I hope to get some time to start updating ThinkTwit again. Apologies to anyone this may have affected but I’ve not seen any complaints so I’m hoping all is well.

PC up and running again

My PC is FINALLY working again! MSI stuck to their work, fixed and returned the motherboard no questions asked, for a small fee of course, although it took about 4 or 5 weeks!

I shall try my best to get working on ThinkTwit again this week and finall roll out the changes I was working on when my system died (I think caching and filters). Sorry again for any trouble this may have caused anyone!

Computer out of action

My computer is currently out of action. Had a lot of trouble with it ever since I built it 2 years ago and it’s only emerged recently that it seems to be due to the motherboard. After a LOT of wrangling with MSI, who make the motherboard, they have finally agreed to repair or replace it for me. After all the trouble though I will probably never buy a product from them again – they are great products and at great prices but their post-sales support is dreadful!

Anyway, this means I don’t have access to my PC or my files and tools so ThinkTwit development is on hold at the moment. Hope to start back up with it in a couple of weeks once MSI has sorted my motherboard out. I apologise if this affects anyone but please feel to write here if you need any help or advice.

ThinkTwit Update 1.1.4

I’ve added another update to ThinkTwit as of yesterday; this includes use of ordered lists (ol) instead of unordered lists (ul) as it is more semantically correct, removed some old code left over from some time back that was no longer necessary, and added the ability to output usernames instead of Twitter names.

The roadmap has been updated – check it out if you want to know what features will be coming soon, and feel free to provide suggestions.

ThinkTwit Update 1.1.2

I’ve today updated ThinkTwit to version 1.1.2 with 2 key changes:

  • Added support for caching engines
  • Added support for CURL

These changes were requested by ThinkTwit users but will no doubt be useful to others out there. The no-caching support uses AJAX (via jQuery) to output code from a pure HTML file (the format in which the cached page is stored) and the CURL support offers an alternative to the standard URL get method which may cause the following error (or similar) if URL file-access is disabled:

Warning: file_get_contents() [function.file-get-contents]: URL file-access is disabled in the server configuration in /..../wp-content/plugins/thinktwit/thinktwit.php on line 145

Warning: file_get_contents(http://search.twitter.com/search.atom?q=from%3Adeleted&rpp=3) [function.file-get-contents]: failed to open stream: no suitable wrapper could be found in /.../wp-content/plugins/thinktwit/thinktwit.php on line 145

Additionally I have added debug messages to assist in locating errors when calling the method that requests the Twitter feed.

I learnt some valuable lessons about creating AJAX capable widgets and maintaining their ability to multi-instance, so I will post a blog on this shortly.

New site

From 14th March 2010 my employment with Think Consulting Solutions is due to come to an end. The decision was mutual as I have shared employment with Connect Assist and it will be easier for me to manage my time and for both companies to progress as partners.

I have, therefore, decided to take ThinkTwit development with me to ensure that it does not die. I needed somewhere to host this and have also planned on having my own blog for some time so decided now would be the best opportunity to do this!

The site probably won’t be updated very often, but I’ll use it to post anything useful probably from a development point of view.