The particular case that causes the problem does not happen to everybody (there’s timing related issues involved, you have to be somewhat unlucky to have it occur), but for those few people that it does happen to, clearing your cookies fixes it. Simple.

It’s also not really a matter of a “bugfix” as it’s a upgrade-process related issue. Once you clear the cookies, the problem goes away and won’t return. Easy.

You have to look at it from a user’s perspective, not a developers perspective. Developers and programmers take things for granted — the obvious is not quite so obvious to everyone.

There will be no fix because there is and was no such problem to begin with. Clearing your cookies *works*. It worked back then too. Some people simply refused to believe me.

Also, it’s amazing how quiet they got after a few days, probably because they realized that they had simply screwed up in some other way.

That’s exactly it. A lot of the things the users complained about with 2.5 have not been fixed in 2.6, so one is wondering what the point of this upgrade was at all because 2.6 was supposed to fix things they “broke” in 2.5 like the widgets page and the sidebar in the write posts page (putting categories back where they belong) among others.

I saw someone the other day say that they wished WordPress would bring back the publish in the future feature, and then another user said hey, it is still there, it is just hidden away from you. So this poor user had been thinking they took away a great feature just because they made it much less usable and really didn’t tell people it was still there and could be used.

They need to realise that people get used to doing things a certain way and when you make a change it has to be to make things *easier* not harder. That is what usability is all about.

Also, Ben – from my understanding, post revisions is going to clutter up databases. As we already know, WordPress is pretty database hungry, so this can only make things worse.

Actually, I’d say it’s more of a weakness with projects where changes are made based on what the developers want, rather than what the users want.

On the other hand, I’ve been in many situations where users haven’t asked for anything new, but developers still make changes and add new things that users actually find useful. Sometimes it is better to be proactive instead only making changes when people ask for them. I’d easily prefer this over hearing excuses for not changing anything ever.

I think it’s important to look at which areas of a system are in need of work. I’d certainly look at that before changing things that people didn’t ask for. Looking at the WP 2.6 changes, I do think that adding post revisions was a good thing. I haven’t looked at the whole list. That one just jumped out at me as a plus.

Somebody help me out here…

If WordPress was optimized for speed in the first place, it wouldn’t have to be upgraded to make it faster. Meh, I’m writing my own.

However at this time I think WordPress has lost all sense of what the people want, and are going with what they want instead. It is around now that they become Microsoft, isn’t it?