Dec 19th Tweetcount Updated: Supports WordPress 2.9, Bitly Pro

WordPress announced the release of version 2.9 “Carmen” today; we’ve updated our WordPress plugins for support. BackType Tweetcount was updated and you’ll need to upgrade to version 2.0 if you’re running WordPress 2.9. BackType Connect did not require an update, so if you’re already running version 0.2.5 you should be fine.

Bitly Pro Support

One of the unique features of our Tweetcount button is its support for custom URL shorteners – we debuted with support for short URLs powered by Awe.sm. Today, we’ve updated Tweetcount to also updated to support Bitly Pro; the button will work with your custom Bitly short URLs. Once you’ve obtained your custom Bitly-powered short URL, visit the BackType Tweetcount options page and enter your API credentials.

Tweetcount now supports: bt.io (default), awe.sm (custom), bit.ly, bit.ly pro, su.pr, digg.com and tinyurl.

Tags: , , , ,

12 Tweets

13 Responses to “Tweetcount Updated: Supports WordPress 2.9, Bitly Pro”

Freakenstein says:

Any plans on supporting wp.me links in the future?
see: http://fusedthought.com/archives/wp-me-shortlinks-now-available-to-self-hosted-wordpress/

Mike Montano says:

Can you follow up w/ us via support [at] backtype [dot] com and I’ll take a look into any tweets we’re missing. We support wp.me, but maybe something is going wrong with the link you tried.

Freakenstein says:

For example,
i’ve written an article about the wp.me feature (sorry it’s in dutch) at: http://freakenstein.nl/wordpress-wpme-selfhosted-short-url/
It’s wp.me short-url is: http://wp.me/pyhRd-OM

When it’s tweeted with the long url, the BackType connect plugin imports the tweet,
but when it’s tweeted with the wp.me short url, it’s ignored.

HOw abt Backtype plugin.. it is not supporting wp 2.9. when will u update it..

It should be working fine in 2.9

Ted says:

Christopher, there is a negative comment that is persisting on the backtype page despite my deleting it. Sure, I understand its persistence in the search index, but why is backtype holding on to it?

We are getting very upset by this. Please contact us ASAP to remove.

Followed up via e-mail

Otto says:

Question that I wanted to pass along to whoever wrote the BackType Connect plugin.

Why in the *world* does it use 12 different cron entries, all of which do the same thing? Yes, 5 minutes intervals, got it, but why not run the thing once every five minutes instead?

I’m trying to figure out if this code is completely idiotic, or insanely brilliant in a way that I have yet to understand, and so I really need an answer here. :)

Please feel free to email me directly with the answer.

-Otto
Moderator: WordPress.org forums.

The valid values for wp_schedule_event recurrence are: hourly, twicedaily, daily. So we run 12 hourly crons 5 minutes apart. Let us know if we missed something.

Otto says:

Ahh, yes, you missed something. :)

You can add your own schedules via the cron_schedules filter hook. Like so:

function my_schedule($schedules) {
$schedules['fiveminute'] = array( ‘interval’ => 300, ‘display’ => __(‘Every Five Minutes’) ),
return $schedules;
}
add_filter(‘cron_schedules’, ‘my_schedule’);

Then just use “fiveminute” as your schedule recurrence.

Otto says:

Sorry for the typos. That should be:


function my_schedule($schedules) {
$schedules['fiveminute'] = array( 'interval' => 300, 'display' => 'Every Five Minutes' );
return $schedules;
}
add_filter('cron_schedules', 'my_schedule');

jim says:

Cool!

Additional comments powered by BackType

Twitter Us

    Categories