WordPress 2.0 Duke

Although it has been avail­able for a few days now, WordPress 2.0 ‘Duke’ is now official.

In fact has already had been down­loaded more than 33,000 times as I write this! You can down­load it from the revamped WordPress.org web site.

There is a lot of new code in this release, most of which is con­cerned with either the Admin­is­tra­tion inter­face, espe­cially the WYSIWYG write inter­face, or under the hood stuff which will bene­fit plu­gin and theme developers. There are a whole bunch of bug fixes too.

There are some very com­pel­ling reas­ons to upgrade to this new ver­sion, but there are a whole bunch of reas­ons to hold off too:

The biggest bug-bear for me is that the Write Post page is no longer usable if you can­not use a mouse. At least, out of the box it isn’t usable (you can­not tab out of the text area for the post). If you can­not use a mouse and have to use the key­board for input, then you need to turn off the WYSIWYG editor. Tab to the Users page, uncheck the “Use the visual rich editor when writ­ing” check­box, and update your profile.

Once you have done that you can at least write and pub­lish plain posts. Alas you still can­not upload images or other media with the new inter­face. That still requires the use of a mouse.

I’m a strong believer in access­ib­il­ity in applic­a­tions, be they web– or desktop-based. I think com­puters, and espe­cially com­puters in com­bin­a­tion with the Inter­net, are a great lev­el­ler. Dis­abled people who per­haps can­not func­tion too well in the phys­ical world have a much more level play­ing field in the online world. Or at least that’s the theory.

WordPress 1.5.2 is a reas­on­ably access­ible applic­a­tion (albeit not too user friendly for those who can­not use a mouse). More by vir­tue of it being pretty stand­ards com­pli­ant than by design. WordPress 2.0 is no longer accessible.

By adding a JavaS­cript based Visual Editor and a bunch of sexy look­ing drag­gable, expand­able con­trols, the applic­a­tion has been rendered unus­able in its single most import­ant func­tion: post­ing to your blog!

It’s a real shame, because the improve­ments in WordPress 2.0 are many, and some of them, like the post pre­view now using your theme, are killer. The new user roles and cap­ab­il­it­ies too are a great new idea and will lead to some good func­tion­al­ity for multi-author and com­munity blogs.

The way uploaded images and other media are handled is much more soph­ist­ic­ated now: they are sub posts and can thus be dis­played sep­ar­ately from the post which con­tains them and have their own comments.

Another reason to be cau­tious about upgrad­ing is that some of your plu­gins may no longer be com­pat­ible. There are a whole bunch that have been checked against 2.0, but there are a whole lot more which haven’t.

In con­clu­sion, if you are think­ing about upgrad­ing to 2.0, make sure you cre­ate a backup first. Turn off all your plu­gins, and even switch back to the default theme. Then upgrade and turn on your plu­gins one at a time. Check­ing noth­ing breaks after each one. Finally switch back to your theme and have a final check.

20 thoughts on “WordPress 2.0 Duke

  1. I am dis­abled (blind) myself so this post is not really encour­aging to me. I still did upgrade though but have not tried post­ing any­thing yet. I might let people know if it is really that unac­cess­ibl as you write (con­sid­er­ing, in the case of blind users, most screen read­ing soft­ware pack­ages offer some­thing like a mouse replace­ment). Still I would be glad if someone could see if there is a way to re-improove this great application’s access­ib­il­ity. As for me, I am prob­ably not enough of a PHP hacker to do it myself :-(

  2. lemme know how the new one turns out
    i will check in out in after the hol­i­days when i know most bugs are com­pleted
    the last thing i want is the blog to crash out like my gal­lery just did (two weeks of utter bs to fix it hehe)
    any­ways hope the hol­i­days are good bud­die
    ps take a peek, the kit­tens are get­ting huge :D
    cheers

  3. Raven,
    You are right there are many com­pel­ling reas­ons to upgrade to ver­sion 2.0
    I’m just cau­tious that dis­abled users might now actu­ally be excluded, which is a big con­cern to me.

  4. René
    I will be most eager to find out your res­ults. I don’t have a screen reader installed, and my test­ing (such as it is) is based purely on key­board access.

    One of the developers, who has taken lots of my com­plaints on board and done much to improve the access­ib­il­ity of this ver­sion, said that the final prob­lems will be addressed in the next ver­sion (though not neces­sar­ily the next release).

    Feel free to write to me privately if you wish.

    Mike

  5. Pingback: Caught in the World "Wild" Web » Why won’t I upgrade to WordPress 2.0

  6. Pingback: Whynet.org - Actualités

  7. What a mis­take, I upgraded and I am now regret­ting it. I lost a whole bunch of use­ful fea­tures, spe­cially in man­aging pic­tures and this updates really did not give me any addi­tional use­ful fea­tures. Now with the task of going back to my last version.

  8. Pingback: JaunsCorner.com Blog » Blog Archive » On Wordpress Accessibility

  9. Pingback: TheBisch

  10. Hi Mike:

    I am a blind user of WP, and I have in fact found sev­eral access­ib­il­ity prob­lems with 2.0.
    The major one is the wysi­wyg inter­face.
    I’m glad the old editor wasn’t scrapped, because if it had, I wouldn’t be using 2.0.
    I’m hop­ing this prob­lem gets fixed.

  11. Amanda,
    Thanks for your info, I’m hop­ing that these issues get fixed in the next release. There has already been quite few fixes sub­mit­ted for vari­ous issues with this ver­sion.
    Mike

  12. The WYSIWYG editor sux! Think I will fol­low your advice for turn­ing it off!

    My upgrade went really well, I obvi­ously had to replace some files because of a manual upgrade, but thats where using your own server pays off!

  13. Pingback: Because I Write » Downgrade to 1.5.2

  14. Pingback: Downgrade to 1.5.2 « LEMP test

  15. The biggest bug-bear for me is that the Write Post page is no longer usable if you can­not use a mouse. At least, out of the box it isn’t usable (you can­not tab out of the text area for the post). If you can­not use a mouse and have to use the key­board for input, then you need to turn off the WYSIWYG editor. Tab to the Users page, uncheck the “Use the visual rich editor when writ­ing” check­box, and update your profile

    nice blog

    Regards
    Timothy

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>