Yesterday I read that the 2.5 version of WordPress was officially released. The cautious part of me wanted to wait to upgrade, but the totally paranoid and non-lazy part wanted to just get it over with. I had read a few mentions of incompatibility, but I decided to just bite the bullet and upgrade.
I hunkered down at my desk, did database and filesystem backups, downloaded the 2.5 release and untarred to my blog directory. Typed in the URL and — poof — there was the blog. Did smoke testing of all the plugins and they worked – every one of them. I was literally done in about 5 minutes.
I don’t think I’ve had an upgrade that wasn’t painful in some way in a long time. This one was nothing. It just worked.
So anyway, long way to say I’m on WordPress 2.5 now. I was shocked at the ease of the upgrade. Later in the day, I saw all kinds of tweets around other people upgrading and having the same fulfilling sense of surprise when they realized they were done.
Thanks to the WordPress team for another great (and uneventful) release.
WordPress 2.3.2 is now available. This release includes some security fixes that should necessitate an upgrade immediately. Details on the release are here. Download 2.3.2 now.
I found this plugin that corrects a pet peeve of mine that I’ve had for a while. The Flickr Blog This To Draft Plugin by Donncha O Caoimh ensures that all of your blogged photos from Flickr come in as drafts, so that you can go in and massage the HTML before publishing.
If you blog photos from Flickr much, and spend time rushing to edit your published picture (to fix HTML, add CSS attributes, etc), grab this plugin to remove the unneeded stress from your life.
One of the biggest arguments you’ll get in deploying open source software in a corporate environment perception that they are extra, standalone applications. If your corporation uses an LDAP server, you can get some big wins by ensuring that your open source applications can authenticate with your corporate LDAP store, showing integration with the main systems.
I recently went through this exercise with a number of applications in our environment, including:
I thought I’d throw up an entry here outlining the tools I used to make this integration possible.
Subversion was a no-brainer, since we host our repositories using mod_dav_svn. Configuring the mod_auth_ldap module in the Apache server and converting all access to SSL made this integration painless, once I figured out how to build Apache to use OpenLDAP and Secure LDAP. For MediaWiki, the Mediawiki LDAP Extension worked flawlessly. The key problem with Mediawiki is that there is no mechanism built in to ensure that logins are performed via SSL. A quick rewrite rule in the Apache server took care of this for me. A complete explanation of this process can be found at Library Web Chic.
For WordPress, I found a great plugin from Kane IT Consulting that was extremely easy to configure. I had the plugin installed and configured in minutes. I highly recommend this one. The Admin-SSL plugin, gave us the security around the login that we needed.
What has been interesting to me is seeing the subtle shift in perception of these applications as we integrated them into the authentication system. They almost seem like legitimate pieces of the system now … even to me.
These are the funniest thing I’ve seen in a while. Check out this wordpress blog that emulates a Commodore 64 CLI. There is also one that emulates a Unix command line. See the test run page or download the theme.
Version 2.1.3 of the WordPress blogging platform has been released and is available for download. According to the WordPress blog, this is a security release that “includes fixes for several publicly known minor XSS issues, one major XML-RPC issue, and a proactive full sweep of the WordPress codebase to protect against future problems”.
I’ve upgraded, and so should you. Take a couple of minutes to do this upgrade, as the possible consequences aren’t worth the humiliation. 😉
The WordPress team has announced the release of version 2.1 of their WordPress blogging software on Monday. A list of the changes can be found in the release announcement.
Sure, this is old news (by internet time standards) but I just got around to getting caught up. I’ve upgraded the site and the process was absolutely painless. All of my current plugins worked as far as I can tell.
For those who have a bit of trepidation over upgrades and the compatibility of plugins, I can tell you that my installation, with over 17 plugins active, seems to be working fine after the upgrade this morning after a total upgrade time of around 15 minutes including backups of my installation directory and database. As usual, the upgrade instructions are available on the WordPress site.
The WordPress team is planning its next release, Version 2.2, around the April 23 timeframe.
I haven’t had a great deal of time this morning to play around, but it does seem that the site runs just a tad bit faster then it did under the previous version.
I’ve been having a real problem with the site being hit hard by spammers lately. Consequently, I have turned comments off on most of the articles on the site at this point.
Due to the implementation of SPAM Karma 2 and Akismet, none of the comment spam actually made it to the blog. I was pretty amazed at how thoroughly these two pieces of software have filtered the incoming comments.
However, the comments not making it to the blog doesn’t mean that the spammers haven’t done any real damage. Twice now I’ve come home to find my comments disabled by my provider, due to basically a Denial of Service attack being executed on the site by these morons.
I found a great page at the WordPress Codex on Combatting Comment Spam. I would encourage anyone currently dealing with this problem to check out this page. I will be implementing some of these ideas one by one over the coming weeks to see how much they help.
I’ll let you know of the success I have. In the meantime, if you aren’t running Spam Karma, I would encourage you to go take a look at it and its corresponding Akismet plugin. The combination of both has been highly effective in this corner of the web.
The folks on the WordPress team have released version 2.0.5 of the WordPress Blogging Application. This release includes around 50 bug fixes one of which was a missing index on the posts table. I just upgraded and the site performs much better now. I had always thought that the site ran a tad bit slower after the 2.0 upgrade, but for some reason I just figured 2.0 was doing so much more than the 1.x versions. Didn’t even think of looking at table indexes.
Mark Jaquith has also put together his list of change files and corresponding archives containing only the changes from 2.0.4 to 2.0.5, along with a patch file to upgrade your stuff directly. I opted to download from the WordPress site.
In any event, according to the release announcement, there are some security fixes in this release as well. As I do with every release of WordPress that contains security release, I am reminding you not to be lazy and get your site upgraded as soon as you can. The performance improvements alone are worth it.
Now … off to see if they fixed that “posting from Flickr mangling CSS thing” …
The WordPress team has released version 2.0.4 of the WordPress blogging software. From the release notes:
This release contains several important security fixes, so it’s highly recommended for all users. We’ve also rolled in a number of bug fixes (over 50!), so it’s a pretty solid release across the board.
This release contains security fixes. As I continuously remind everyone since being hacked, don’t be lazy on these upgrades!
Needless to say, I’m done.