Mike Industries switches to WordPress

Mike Davidson, CEO of the very cool Newsvine, switched from Movable Type to WordPress three months ago, and spent some time listing his reasons for doing so. Consider this the antidote for any WordPress community members who were feeling a little bruised by Anil Dash’s recent article about switching in the opposite direction.

Aside to Mike: are you planning on attending Gnomedex this year? Rumored to be the weekend of August 8th. I’d love a chance to meet you.

Aside to Anil: I swear I’m going to reply to the technical points of your WP 2.5 article eventually. There are a few points that merit correction, and other points that deserve a response.

WP 2.2 is a mandatory upgrade for 2.1.3 users

Just a quick point of clarification. WordPress 2.2 is a mandatory security upgrade for WordPress 2.1.3 users. There will be no further releases in the 2.1.x branch. 2.2 includes security fixes that 2.1.3 lacks, so your only upgrade path is to 2.2.

The good news is that although a lot of under-the-surface code changed in 2.2, it’s not jarringly different from a usage standpoint. So if familiarity was holding you back from upgrading, it shouldn’t be.

WordPress 2.0.9 Upgrade: changed files ZIP, changes diff, changed files list

WordPress 2.0.9 has been released, incorporating a security fix, and a few other bug fixes. This is a mandatory upgrade. If you want the full zip with the entire WP install, download it here.

If you are upgrading from WordPress 2.0.7, you obviously don’t need the entire install, you just need the files that have changed. Because my upgrade files for 2.0.3 through 2.0.7 were so popular (and thanks to countless words of praise and even a few generous monetary donations), I’m going to continue to provide the same files for this and future 2.0.x upgrades.

Changed Files List

Changed Files List (2.0.7 » 2.0.9)
This is a list of all the files that have changed since the last (2.0.7) release. You can also see the changes and their corresponding tickets on Trac (since 2.0.8) and Trac (since 2.0.7) .

Changed Files ZIP

Changed Files ZIP (2.0.7 » 2.0.9)
This is what most people will want. This is a zip file that includes only the files that have changed since the last (2.0.7) release. This will save you a lot of FTP upload time. Note that this does not include anything in the /wp-content/ directory, to keep you from doing something stupid like overwriting all your plugins and your themes. The Akismet plugin is maintained separately, and there is a new version available. Please download the latest version from akismet.com.

Changes Diff

Changes Diff (2.0.7 » 2.0.9)
This is a diff file (a patch) with all the changes made since the last (2.0.7) release. Make sure you do a trial run by using the patch command’s --dry-run (or equivalent) switch, to verify that the patch will apply cleanly. I’ve omitted the Akismet upgrade from the diff to prevent patch conflicts. Please download the latest version from akismet.com.


I prepared these files myself and have tested them. Still, I cannot stress enough the importance of making a full file and database backup before attempting to upgrade WordPress using these or any other files. I cannot be responsible for your carelessness. Make a backup!

I should mention that these files are unofficial. They were made on my own time, of my own volition, without any input from other WordPress developers and without any official sanction from Automattic inc.


One of my favorite things to do when I come across a new WordPress-powered blog is to type ?s=wordpress into the address bar, which searches their site for posts mentioning WordPress. I like to get a read on what people think about the engine that powers their thoughts. While I enjoy the ones that offer praise and appreciate the ones that provide constructive criticism, the best result is when I get zero hits. That’s when I know WordPress is doing its job: when people aren’t even aware they’re using it because they’re so busy using it!

I’ve heard a lot of Social Media Prophets proclaim that the tools don’t matter, that it’s all about the content and the connections being formed.

Ideally yes, the tools shouldn’t matter. The tools should be so intuitive that our awareness of them fades to nothingness. But as long as ?s=wordpress keeps returning hits, they do matter. In fact, the sure sign that we’ve reached the point where the tools don’t matter is when the statement “the tools don’t matter” is so obvious a statement that no one would waste time making it.

I have no idea who’ll use this, but why not?

Seen on the changelog for Paparazzi!, a clever OS X app for taking full-height screenshots of websites:

JPEG 2000 export (under Tiger). I have no idea who’ll use this, but why not?

The moment you see that on a WordPress changelog message, it’ll be time to jump ship (or rather, “fork ship”). The question answers itself: because there is no obvious benefit, and there are several hidden costs.