Avoid Wordpress 2.6

[RawAlex]

If you happen to get the urge to update, don't.

Disaster. You will potentially lose access to the admin, their new posting system saves revisions in the same database as posts, which means every typo correction makes an entirely new post, so the data files will fill rapidly, and xmlrpc and all it's ilk are disabled by default.

This is an "avoid" upgrade.

[tony404]

Originally Posted by RawAlex

If you happen to get the urge to update, don't.

Disaster. You will potentially lose access to the admin, their new posting system saves revisions in the same database as posts, which means every typo correction makes an entirely new post, so the data files will fill rapidly, and xmlrpc and all it's ilk are disabled by default.

This is an "avoid" upgrade.

its almost like no one tests it before they put it out there. lol

[Top_Of_Google_Man]

i avoid wordpress period.

[pam]

I've upgraded 3 sites today and love it. Image uploading is much cleaner, faster and easier. No issues yet, all plugins work fine.

[Toby]

I have just one blog. I upgraded Monday evening, and no issues. In fact it resolved a couple of issues that I was having with the admin.

[RawAlex]

You are lucky... their board is packed full of people with dead blogs, blogs they can't log into, and various other nice issues.

[pam]

I see that with every upgrade. Mine were done by accident as I was trying to upgrade to 2.51 and forgot a new version was out. A lot of it depends on plugins, I feel -- I had a broken blog a while back with 4 years of posts and was heartbroken, but it was a plugin and that's all

[Footman]

I just upgraded one of my blogs and everything is fine. Thankfully so. Like Toby it seemed to clear up an issue I was having with the previous version.

[Hammer]

It's been working OK for me.

[SinSational]

interesting...
we've been doing some research on 2.6 and were going to suggest people upgrade.
2.5 had major security issues, so we suggested people upgrade to 2.5.1 but 2.5.1 has coding flaws that cause extreme server loads. safe to say there will always be issues with free scripts.

[Toby]

Has anyone come up with an easy way to turn off the saved revisions "feature"?

[RawAlex]

Originally Posted by SinSational

interesting...
we've been doing some research on 2.6 and were going to suggest people upgrade.
2.5 had major security issues, so we suggested people upgrade to 2.5.1 but 2.5.1 has coding flaws that cause extreme server loads. safe to say there will always be issues with free scripts.

The coding issues of 2.5.1 are somewhat fixable. There are no published large security holes in 2.5.1 (but a couple of small ones may exist). But the original build of 2.6 was a horrible piece of crap, untested with many very basic errors. It was a shocking bad release, that is for sure. Basic errors from the permalinks not working to people getting entirely locked out of their admin areas... not new feature bugs but in fact poorly tested fixes.

I think the current build is a bit better, fixes some issues, but other issues are for 2.6.1 or even 2.7. These guys are terrible for breaking shit and not checking.

Don't get me started on their stupid revision code that dumps all those revised posts into your wp_posts database, and then makes the entire site performance suffer by having so many more records to search through each time.

Toby, you can turn it off by adding code to the program, but I am not sure where. But it will get wiped out again at your next update.