I broke my website today - I broke it bad. But because I am Just That Slick, I was able to repair everything without anybody noticing. Well, I did get one e-mail from a friend letting me know something was wrong, but I e-mailed her back and said something to the effect of “you caught me with my pants down!”
The reason I needed to repair everything was because I improperly tried to move the files in http://www.amanita.net/wordpress into http://journal.amanita.net so I could use the cookies for password-protected posts. (If you’re reading this on LiveJournal, posts that are friends-only on LJ are password-protected on my website.) So I tried to switch and - kaboom! Everything was all screwed up, I couldn’t log in anywhere, and things were Not Good. So I figured I needed to reinstall WordPress. After some fussing with the tarball, I was able to get everything uploaded where I wanted it. In order to make the install go smoothly, though, I renamed my original database - the one with all the config and posts and comments and everything - to etoile_backup. I then created a new database for the journal, ran the WP installation normally, and had a nice mostly-empty journal database. The scary part was dropping that database altogether and then renaming etoile_backup back to what my journal database is supposed to be called. I was a bit nervous that it would break stuff, lose my archives, etc. but everything went smoothly. Oh, and did I mention I was doing all of this database creation, renaming, etc. in cPanel and phpMyAdmin using Lynx? Yeah, I told you: I Rule.
I moved my plugins and my themes over too, and everything seems just fine. Phew! I don’t have the alternate admin CSS that I used to, but I was getting tired of that anyway. Now I just have to find the courage to delete the old wordpress directory - I’m paranoid about that kind of thing. And those of you who have my password for posts - it should be working now.
Hmmm, maybe it’s a sign you should go back to MT!
ha ha, just kidding, you know I’m just teasin’ ya!
[...] Thanks to the very astute Levi, I have found and fixed a problem with my feeds. For some reason WordPress includes an XML declaration that FeedBurner can’t handle, so I had originally edited that. When I reinstalled WordPress recently, it overwrote the feed files I had edited with the incompatible ones. Levi called my attention to my broken feed, and it took me a few minutes to figure out what the problem was. As soon as I did, though, I edited all of my feeds by hand and got rid of that bad declaration. Poof! Problem solved, and my feed is up and running and happy again. If you haven’t already subscribed, there are some handy links to do so right on the burned feed itself. [...]