It’s been five years since Matt released WordPress 0.7. I think it’s quite an accomplishment that (and how) WordPress has managed to evolve into a very mature blogging solution with all the right features and no bloat whatsoever. I switched to WP (from Movable Type, like so many others) in 2005, and it has since become my favorite CMS solution. I’ve been using it professionally for a while now, and have made quite a few customers very happy.
So here’s to you, WordPress. May you continue to evolve the way you did!
I used to get files like this from Mark Jaquith’s website, but hasn’t released changed files packs for the last couple of upgrades. The zip below contains all files changed from version 2.2.2 to 2.2.3. If you, like me, run several WordPress blogs, uploading the changed files alone can really save lots of time.
WordPress 2.2.3 changed files
Please read (and follow) the upgrade instructions, although this particular upgrade does not require you to run the upgrade.php script. If this doesn’t work for you you’re on your own. It worked just fine for me though :).
For a project at work, I needed to set up a bunch of blogs yesterday. All with pretty much the same setup and no special needs like exotic plugins or anything. Instead of going through WordPress’ famous 5-minute install six or seven times I decided to try WordPress MU. Considering how MU is a solution aimed at sites looking to run thousands of blogs off of dedicated servers (it’s being developed at wordpress.com), I thought it would be hard to install and pretty much unusable by mere users like me. But instead there was almost nothing to configure and the installation is even easier than that of a regular WordPress install. Go figure.
(more…)
WordPress.org has just released a critical update for their blogging software. Version 2.1.2 fixes malicious modifications that were introduced by a hacker who somehow got access to the download server. Or as Matt puts it:
Long story short: If you downloaded WordPress 2.1.1 within the past 3-4 days, your files may include a security exploit that was added by a cracker, and you should upgrade all of your files to 2.1.2 immediately.
I’ve just finished upgrading my blogs, and you should to. Spread the word!
