WP 2.1 Breakage
So I upgraded to WordPress 2.1, and it immediately broke stuff. For example, check out the RSS feed validator’s results for the summary version of my all-posts feed (full-content feed validation results; same problem). I think it’s just so cool how the software manages to get the sever to return a 404 for a file that’s clearly being served.
Of course, I only got to that point after commenting out the IfModule mod_rewrite.c stuff WP apparently tacked onto the end of my .htaccess file. Before that, the above-referenced feed URLs just brought up the home page of the site while preserving the feed URL in the address bar. Keen.
Exactly the same progression of trouble has applied to the Distractions feed, too. At first the server (or WP) was filling in the home page, and now it returns the feed along with a 404 response.
I’ve also had the same problems with the main page of the post archive—at first, it redirected to the home page. Now it just returns a 404, although unlike the feeds, it doesn’t also create a full page to go with the 404. At least, I don’t think it does. I can’t see it, anyway. A shame, too, that it does its own thing rather than use the 404 page I already defined in the .htaccess file.
Anyone have any guesses at all as to what’s going wrong, and how I can get WP to stop throwing around inappropriate 404s? I assume this has something to do with my .htaccess file’s Rewrite rules—which worked just fine in WP 1.5.2, by the way—and the new error handling routines. Or maybe it’s just the new error routines.
Oh, and while we’re at it, what’s the story on the “new tabbed editor” that’s supposed to let you “switch between WYSIWYG and code editing instantly while writing a post” that was mentioned in the WP 2.1 announcement? Because I’ll be switched if I can find it.
Ah, the joys of upgrading…
Addendum: anyone know of a quick and simple way to just disable WordPress’ internal rewrite code, so I can go back to using my .htaccess file? That might solve the problem just as well as trying to hack my way around the problem with WP, and a lot more simply.
