The Noisy Channel

 

Upgraded to WordPress 2.7

December 11th, 2008 · 6 Comments · Uncategorized

Just wanted to let readers know that I’ve upgraded to the latest version of WordPress, 2.7 (“Coltrane”). Please let me know if you experience any technical difficulties.

If you enjoyed this post, make sure you subscribe to my RSS feed!

6 responses so far ↓

  • 1 Dave Fauth // Dec 11, 2008 at 3:29 pm

    Was it an easy upgrade? Any advice?

  • 2 Daniel Tunkelang // Dec 11, 2008 at 3:51 pm

    My advice is to install the WordPress Automatic Upgrade plug-in, which makes the process painless.

    http://techie-buzz.com/wordpress-plugins/wordpress-automatic-upgrade-12-release.html

  • 3 Brian Davson // Dec 13, 2008 at 3:07 pm

    I was really hoping you’d make some change that would auto-magically fix the problem I’m seeing with my Flock browser. Your feed (still) shows all entries with the same modification time. (None of the other couple dozen feeds I subscribe to have this behavior, and yours didn’t before you moved to WordPress.)

    Generally speaking the most recent posts are at the top, but it means that I either re-read posts that don’t look familiar and posts I was saving to read later tend to become invisible pretty quickly.

    I use Flock intentionally only on my home computer (rather than a feed-reader service) so that I am not tempted to read blogs all day at work…

  • 4 Daniel Tunkelang // Dec 13, 2008 at 3:30 pm

    Brian, this is the first I hear of this problem. Is anyone else here experiencing it? If not, perhaps it’s just a bug in the Flock feed reader?

  • 5 Brian Davson // Dec 13, 2008 at 3:48 pm

    It could certainly be a Flock bug, and while annoying, the problem hasn’t risen to the top of my stack to look into it deeply. The problem has persisted through both a major and at least one minor Flock update, though.

  • 6 Daniel Tunkelang // Dec 13, 2008 at 4:34 pm

    The Noisy Channel doesn’t discriminate against niche browsers. But I’d like to know that at least one non-Flock user is seeing this same issue before looking into it as a bug on this end.

Leave a Comment

Clicky Web Analytics