Woo hoo! It’s the weekend: WordpPress.com 2.5 upgrade

My blog interface just changed to 2.5 without any prior announcement. I imagine it’s going to be an interesting weekend on the wordpress.com support forums for two reasons.

(1) Most wordpress.com bloggers that I know haven’t bothered to test drive the new interface on the demo site that I posted about previously.

(2) Those who haven’t done the test driving will be unaware of the functionality changes when it comes to widgets.

Mark has now placed a sticky post at the head of the forum containing instructions. But based on my history of answering over 7,000 questions there, I’m betting that most bloggers probably will not read it.

Related posts:
WordPress 2.5 Upgrade Changes for WordPress.com bloggers
WordPress 2.5: An Easy Upgrade Guide

Here’s the official announcement.

add to del.icio.us :: Add to Blinkslist :: add to furl :: Digg it :: add to ma.gnolia :: Stumble It! :: seed the vine :: reddit :: furl :: TailRank

37 thoughts on “Woo hoo! It’s the weekend: WordpPress.com 2.5 upgrade

  1. Pingback: TeckLine

  2. @rain
    Matt hired happy cog to do the original design work and they are numero uno. It’s too bad he felt he had to muck with their design but not surprising. It’s Shuttle all over again.

    With the number of outstanding tickets pertaining to 2.5 functionality issues that arose with self-hosting bloggers from wordpress.org after upgrading, one would think that the way to go was “‘fixing” the bugs that were reported by the self-hosting bloggers before doing the wordpress.com upgrade. It seems there are about 888 outstanding tickets pertaining to functionality (according to disfunctional’s forum post) but the program was “full steam ahead” so I’m not surprised by the fall-out.

    “I haven’t tried much, so I haven’t experienced breakage.”

    As far as you answering forum questions to solve technical problems I’m convinced that without Richard providing the testing and the answers on 2.5 first for forum volunteers, that you would have no 2.5 answers to give but do correct me if I’m wrong. It’s a good thing that staff worked on this throughout the weekend because they are the only ones with backend access. And when volunteers muck about instead of sending bloggers to staff on technical things, they merely frustrate the process and delay the bloggers from getting the technical assistance that they need, thereby heightening emotions.

    Change always upsets people. I had repeatedly tested 2.5 on the demo site previous to its sudden announced arrival at wordpress.com so, setting aside the functionality issues, I did not find it disturbing. I even posted on this blog encouraging wp.com bloggers to try out the demo site but then I watched wordpress.com bloggers go on about their merry way rather than doing so.

    When the change was made the wp.com users, who had no prior notice, reacted by becoming emotional. Who can fault them for that? After all what we experienced once again was management by stealth. Of course the chorus of the fanboys who laud and applaud every change made can also be heard. Heck they have even been posting into forum threads acting as wordpress apologists when they have no answers to give to the questions posed by the bloggers who posted them.

  3. I have to say, I’m finding the new dashboard to be a radical improvement on the old, for reasons I have difficulty articulating. It’s like going from a c prompt system to an iMac. It’s just far more intuitive for me, and I adore having the stats on the main Dashboard page. I find the navigation much easier and the layout less “business blue” and stark.

    That said, I haven’t tried much, so I haven’t experienced breakage. I posted a YouTube, edited a comment, and posted an image, all without any issues whatsoever. Usually my system is the first to show problems, because it’s so old.

    PS: the ID number is available from the Edit->Preview or from mouseover on the Manage Posts page. I certainly hope they make a column on that page for it, though. Seems a strange omission.

    And I do wish people would keep their emotions out of the forum. Really, I’m sure every volunteer there is kinder than me but it must be said I don’t go there to help people work through the stages of grief; I go there to solve technical problems.

  4. Those of you who are still experiencing problems can use the “support” button on the top right hand corner of any admin side blog page to report the specific details to staff. Please remember to include your blog’s complete url starting with http:// your operating system, your browser and the version of it that you are using as well as, a very clear statement of the problem. Also note that are there are 888 support tickets at this time that it may be quite some time until staff can get to yours.

    If you’re experiencing problems uploading images, please make sure you’re running the current version of Flash. Confirm that here: http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_15507 It probably won’t solve all issues but is a necessary first step.

    If you’re wondering how to use the new uploader to add an image to your post, please see Matt’s short screencast here: http://faq.wordpress.com/2006/07/16/how-do-i-upload-pictures/

    For additional suggestions consult Richard’s post.

    If you are no longer able to find the ID number of a Page so you can exclude certain Pages from your Pages widget then you are not alone. There are also reports that the Author’s widget no longer functions.

  5. You folks are making me wonder if I made a mistake just now installing WP on my site. After the install, there was a link that said “update available” or something like that and I followed it. I just sent support at my hosting company a note asking about updating.

    In the past, I’ve used MoveableType over at my blog at http://www.unspun.us (which lately is mostly on blogatus). I’m wondering if I should have stuck with that.

    Well, what’s done is done (for now). I’m going to give things a whirl.

    On the other hand, my new Probable Cause (www.rhedefense.com/blog) got installed with some older version of WP.

Comments are closed.