The new Twitter Widget Pro support forum has turned up some great ideas and has helped catch some easily missed bugs. This latest release of Twitter Widget Pro includes a bugfix that removes a duplicate closing tag for the title link, which was caught by someone in the forums, as well as an enhancement that makes the date format a per-widget setting (also suggested int he forums).
There was a small formatting issue introduced in Twitter Widget Pro 2.1.0 where there were no spaces between the tweet and meta data or between the date of the tweet and where the tweet was from (such as “from TweetDeck”). When I added the shortcode functionality I had to remove a lot of the excess whitespace so that the formatting built in to WordPress didn’t mess up the formatting of the widget when it was embedded in a post or page. I just released version 2.1.2 that fixed the spacing without messing up the formatting for the shortcodes.
I also added in some links to the WordPress Twitter Widget Pro Support Forum to make it easier for you to ask questions or make suggestions or requests. For more information, go to the Twitter Widget Pro page.
Recently, a Twitter Widget Pro user (alx) asked on the support forum for a new feature. He wanted to be able to have all the links open in a new window, and that’s a great idea! I just released version 2.1.1 of Twitter Widget Pro with this exact feature. If you want to request a feature, or need support, go to the Twitter Widget Pro Forum. For more information, go to the Twitter Widget Pro page.
I just tagged a new version of Twitter Widget Pro which includes an oft-requested feature, a twitter-widget shortcode. You can now embed a twitter widget into any post or page by simply dropping in a shortcode like [twitter-widget username="xavisys"] to embed a widget like this:
I just uploaded version 1.3.0 of my WordPress Twitter Widget Pro plugin. It has been updated to allow HTML in the title and error message, which will allow for more inventive titles (like the one currently being used in the sidebar here). Additionally, the plugin no longer relies on you having a caching solution installed and set up. It now caches the tweets for 5 minutes using the built-in blog options functionality. Twitter limits the number of requests you can make in any given hour, so this caching should greatly reduce the number of times you see the “twitter not available” error message. Lastly, we phased out the old Snoopy class in favor of the new HTTP class.
Please discuss this plugin on the WordPress Twitter Widget page.
I just uploaded version 1.2.2 of my WordPress Twitter Widget Pro plugin. Since twitter has slowed down, a lot of people (especially on slower servers) have been getting the “Could not connect to Twitter” message when twitter was slow but not down. I’ve added a setting on each widget to specify the number of seconds to wait for Twitter. It still defaults to 2 seconds, but you may have to bump it up. Just remember that when twitter IS down, it will try for that full amount of time to reach them BEFORE your page loads, so don’t set it too high!
Please discuss this plugin on the WordPress Twitter Widget post.
I just uploaded version 1.2.1 of my WordPress Twitter Widget Pro plugin. It includes the removal of the “friends feed” option, the addition of custom error message setting for when Twitter is down, and optional anonymous statistics collection (more on this in a moment). Unfortunately, the database query that Twitter had to run to retrieve these feeds was contributing to their constant crashes. They have removed this functionality, and have no immediate plans to add it back. If they ever do, I’ll redo the plugin to use it. I’m sorry, but it’s completely out of my hands.
Regarding the anonymous statistics collection, as my plugins are getting more and more popular (1000s of users now), I’m struggling to keep in touch with my plugin users. Gathering some statistics will help me to design my plugins to meet the needs of the users. This is not meant as an invasion of privacy, and you can easily disable it from the options page.