I decided to try the WordPress 2.6 Upgrade. I started the nailbiting consideration a couple of months ago. Last week I finally actually did something about it. If you follow me on twitter, you may have seen threats, promises and innuendo about me upgrading for the past couple of months.
Before: http://whall.org/blog, WordPress 2.3.3. The blog has been upgraded through many iterations, including pre-2.0. I’ve been blogging for more than three years now.
During: http://whall.org/test26, Installed WordPress 2.3.3, imported posts from previous blog, put in all the same plugins and as much as the same config as I could. Upgraded the test install to 2.6. Got bored. Procrastinated. Went crazy once.
After: http://whall.org/blog, WordPress 2.6.1. Imagine the hotness!
The complete log of my attempt is in the extended entry. It’s long and boring, like some contracts you might sign, or 90% of an RNC acceptance speech. So I hired a comedian speech writer to put in a bunch of one-line zingers here and there. I’m fully expecting the left-wing blogosphere to launch an all-out attack on my family any day now.
- Made a subdomain test26.whall.org but then decided I didn’t want to wait for DNS to propogate so I’m just using /test26 on the domain. I do this via the Admin console provided by my ISP.
- Created /test26 folder in my home directory at my ISP. I do this via an ssh session. I’m very quiet about ssh.
- Created a MySql 5.0 database (this is different than my existing blog database, which is MySql 4.0 – unsure if it will be an issue). I do this from the MySQLAdmin console through my ISP. This may prove to be a mistake, and it might make me sob. It’s MySql and I’ll cry if I want to.
- Unzipped wordpress 2.3.3 installation files (I kept it around) into /test26 directory. zzzzzzzip!
- Followed typical wp-config-sample.php editing and copy to point to new MySql database, then followed typical installation by going to wp-admin/install blahblah. There really should be a blahblah unix command.
- Changed some general options through the wordpress admin interface. To be specific, I changed the “general” options.
- Copied all the plugins for my main blog over to the test blog – first I cd into the main blog wp-content/plugins directory, then run this command
tar cvf – . | (cd ~/test26/wp-content/plugins/; tar xfBp -)
I’m so glad(e) my plugins worked! (plug it in, plug it in)
- One by one started activating the plugins on test26 blog. I noticed that Akismet and WordPress Video Plugin have updated versions, so to be fair, I should upgrade those before continuing. But I don’t think “being fair” was listed as a requirement for upgrade.
- That reminds me – I should give a list of plugins I have activated on my blog. Here ’tis
- Add Meta Tags, v1.6
- Akismet, v2.1.5 (2.1.6 is available)
- Browser Sniff, v1.10
- Commentluv, v1.92
- FeedBurner FeedSmith, v2.3.1
- Flash Tag Cloud, v0.3.2
- Get Recent Comments, v2.0.2
- Gravatars2, v2.7.0
- Headline Images, v2.7
- Kimili Flash Embed, v1.4.2
- Maintenance Mode, v3.2
- My Top Commentators, v1.0
- SpotMilk, v2.2.1
- Subscribe To Comments, v2.1.2
- Twitter Tools, v1.1b1
- WordPress.com Stats, v1.2.2
- WordPress Database Backup, v2.1.5
- WordPress Video Plugin, v0.66, upgraded to 0.67
- WP-Cats, v0.2
- WP-Polls, v2.21
- WP-Polls Widget, v2.21
- WP-Syntax, v0.8
- Upgraded Akismet from 2.1.5 to 2.1.6. And there was much rejoicing.
- Added API keys to Akismet and WordPress.com Stats plugins. And there was 50% as much rejoicing.
- Realized this would be better if I had some screenshots. And the rejoicing thrusters are now at 10% power.
- Attempted an export of old blog via Manage -> Export.
- Hmm, I’m getting a Error 500 – Internal server error, an internal server error has occured! Please try again later
This, I don’t like. When as trying again ever helped someone?
- So I start to troubleshoot this error. Looking at my access.log.current, I notice some forum on Miley Cyrus is using my LOL-YOU-SUCK image.
Clearly, these people suck.
- I see in the logs where I requested the export, but I don’t see any errors. Maybe this server’s Apache puts errors in another log. This is like reading a Tarot spread, I swear.
- Can’t find another log.
- I look closer into the access log for the export errors.
- I see my browser doing
- Then one second later, my browser (IP) but the export page itself is doing
- Then same second, doing
- Then same second, doing
- Then 5 seconds later, doing
- and I believe that’s the one that dies. Belief is what separates humans from the animals. That, and deoderant.
- The second attempt has similar logs from above but just has the original export.php, then polls-admin-js, then the export.php?author=all line, so perhaps the Akismet upgrade is different?
- I’m about done with this crap. Seriously.
- I see my browser doing
- To rule out the server code and what not, I try an export of the NEW test26 site and it gives me an .xml file.
Have you heard the word “whatnot” today? There’s a funny line in Rushmore with it. Google it.
- I try to go directly to the “5 seconds later” URL and take out the %C2%BB parts but still an error. Everything’s better without the %C2%BB parts, doncha think?
- I try to restrict author to just one author, and it still craps out. Offending URL is still the same but it says author=1 instead of author=all.
- I google
wordpress export.php error 500 internal server
- I’m not encouraged by the results.
- Ugh, got interrupted.
- I posted my export issue on a wordpress forum.
- Taking a look at the WordPress to WordPress import plugin
- Realizing after a while that I think this is what got put into WordPress 2.3.3 as a default feature. So much for that.
- Time passes (approximately one month).
- WordPress 2.6.1 gets released. Ugh. Might as well start over!
- I decide to just do a SQL backup, a WordPress database backup and a file backup and just follow the directions in the upgrade instead of testing anything.
- Deactivate all plugins
- Overwrite the files
- Run the upgrade URL
- Check out my theme (make minor tweaks, like for gravatars)
- Re-activate the plugins one by one.
- Oh, my, gosh the auto-upgrade is FANTASTIC!
- Now I’m all and upgraded. Woohoo!
- I download “gears” to make things “faster”. All it ends up “doing” is putting unnecessary “quotes” around the things I “type”.
- I notice I still can’t export. I still get error 500. Sheesh! It must be something in my specific database because the export of a barebones 2.6 install worked fine. Should I get some expectorant or laxative for my blog?
- As I finish typing this up, WordPress alerts me that 2.6.2 is available
- WILL THE INSANITY NEVER END?