Rmedia

Oh, this is really embarrassing.

Somehow, someway,one of our admins turned off mod_rewrite during the upgrade process. Don’t ask me how, because frankly it was a fluke.

I have been misattributing a problem to WordPress that is a result of our own error.

I feel so terrible. Really I do. I look back in frustration and I feel like such an ass. I was just flustered.

Please forgive me.

We got 3.1 working.

It was not, I repeat NOT a problem with WordPress itself. 100% our fault.

I’m sorry.

Fair enough, here is my solution:

I installed 3.1 fresh, in a directory with no files.

I installed the old WP installation on another domain, and we are literally copy/pasting articles from that site to the new one. All 10,000+ of them.

It will probably been the end of the week until we are finished, but it works, and it is the ONLY thing that has worked for us.

We could stick with the old site, I suppose, but I fear what will happen when 3.11 is released. We just need to get over the hump, and nothing listed above did anything at all.

You have to do what you have to do.

I suppose the issue is solved.

Look, I’m not arguing, I just find it frustrating. You would too.

The other thing I just .. don’t … understand is why if something as complicated as say, Drupal, can release updates without touching the database, why WordPress always has to [moronic expletive deleted] around in the data for even the most minor upgrades.

Leaving the data alone would be a HUGE step in the right direction for stability. Either that, or only touching the data when there is just no other alternative. It should be a last resort.

It would make going back and forth in versions so much easier.

I just loaded a completely fresh install of 3.1, it works and it’s nice, but as I was going through it, I kept wondering “they needed to munge my database for this? I don’t get it.

If the decision is to include a minor feature and touch the database, or omit the minor feature and leave the db alone, I overwhelmingly vote for the latter. That’s just my opinion.

Stability is everything.

Everything.

Yes, I tried it all.

Ended up having to scrub the site. Even the restoration back to the previous version was borked (apparently there have been numerous database changes between our version and this one).

We have to go back even earlier and it’s taking all day to restore (and probably tomorrow as well)

Our site was in WordPress for 5 years. That’s a pretty good track record, I will admit.

This release, though … well … I’m sorry, really sorry, but it’s just inexcusable. Some bugs here or there are of course understandable, but this was a showstopper on a pretty basic LAMP server that has been up 600 days without a single hiccup.

Not just the bug, but the fact that nobody is really sure how to fix it.

It’s a mess. An unmitigated mess. An effing disaster if you may pardon my french.

Sometimes, it’s better just to leave well-enough alone, and I wish we would have.

I love WordPress, I really do, but man … what was who smoking when they decided this was ready for prime time?

Same here. Completely hosed permalinks.

I’ve spend the last few hours trying to get them back, but no dice.

This is why I generally don’t upgrade. Before this, I skipped the last 5 or so releases.

If I have learned anything, it’s that it it ain’t broke, the chances of an “upgrade” breaking it outweight having an older version.

I wish I had gone with my gut longer. Next time I get a stable release, I am not upgrading again unless I really need a feature desperately.

IMHO, software is actually getting less stable, not more stable.

I’ve used Linux for 10 years, and Ubuntu 10.10 is the only one that has ever locked up on me (and it’s done it about 8 times now).