When I was shopping for a hosting company, there were a few final contenders in consideration. But Slicehost hit a sweet-spot in the variables of price, host stats, and that certain je ne sais quoi that tells you that a company seems to Get It. “Built for Developers” — that’s a good start right there. You want Plesk or Webmin? They don’t give it to you. But you can install it yourself if you really want it. Yeah, baby — that’s my kind of hosting.

ShareThis

Okay, people, if you are running any version of WordPress older than 2.3.3 2.5*, you need to upgrade now. Seriously. WordPress 2.3.3 and older have security holes that are being actively exploited by hackers to inject spam links into blogs which are not maintained. And search engines like Technorati are de-listing hacked blogs. Are you listening now? Do I have your attention? Upgrade your web apps before you get hacked and your site drops off the search-engine radar.

While the Technorati article specifically talks about WordPress sites, this goes for any web application. You need to pay attention to updates which are released, and upgrade whenever a security probem is fixed. WordPress gets particular attention due to its popularity and the sheer number of installed sites out in the wild. But it is no more or less secure than any other similar web application. So whatever you’re running, keep it up-to-date.

And the same goes for any add-ons — if you install third-part plugins or themes, make sure you keep up with updates. WordPress 2.5 makes updating plugins easier than ever. Review your Plugins page from time to time, and pay attention when it tells you that a newer version of a plugin is available.

I see comments from people all the time saying that they don’t want to upgrade because it might break this theme or that plugin that they have installed. To those people, I say, GET OVER IT. The security of your site is important. If some theme or plugin is not compatible with a newer version of WordPress, ask the author politely to update it. Or find a replacement. Or live without it. I have in excess of 25 plugins active here. But there’s not one of them that I would hesitate to deactivate when it comes to security of my site.

There are several ways to keep up with new WordPress releases. The Dashboard shows you all sorts of news from the WP community, including announcements from the Development Blog. There are several mailing lists. If those lists are too noisy for you, you can get just release announcements by signing up on Freshmeat.net and subscribing to the WordPress Project. I normally submit the Freshmeat update within 24 hours of an official release.

* One exception is WordPress version 2.0.11 (or the 2.0 svn branch, more generally), which is maintained with security updates for the Debian package.

ShareThis

There are a host of technologies and tools from Microsoft that can add value to your PHP solutions, save you time, and are just plain cool. This presentation will cover server technologies like FastCGI, IIS and the PHP SQL Server Driver, client technologies like the ASP.NET AJAX Library and Silverlight, as well as developer tools. This is not a sales pitch – it’s a technical walkthrough with demos, and will give you pointers to lots of resources for digging deeper.

I’m sure Glen’s talk will be interesting, and I’m looking forward to a chance to catch up on the current state of web servers in Microsoft-land. While I tend to use unix-based systems for most of my own work, there are plenty of organizations who are standardized on Microsoft products, and you have to be able to be able to work with what they have. Case in point, my wife is hoping to set up a WordPress website for her department at work, and they’ll probably set it up on a Windows-based server.

If anybody reading this is planning to attend, please introduce yourself. I’ll be wearing a WordPress shirt.

ShareThis

First of all, in my post about Release Candidate 1, I mentioned that I had problems with the plugin updater. Since that time, I have been able to upgrade complex plugins with out a problem. I didn’t do extensive testing, but I feel like this is probably safer now. Other folks on the wp-testers mailing list have reported observed improvements similar to mine.

Next, I’ll point out that since the introduction of the WYSIWYG editor back in version 2.0, I have always stuck to the “Code” editor. And on top of that, I have disabled the auto-formatting (wptexturize and wpautop) filters. I’ve always entered every bit of HTML within my posts by hand. Starting with version 2.5, I’m going to relax my grip and hand the reigns back over to the system. I’ve disabled my “untexturize” plugin, and switched to the “Visual” editor as my default. The Visual editor should be just fine for most of the posts that I write. And on those occassions when I need to do something advanced (like <code>, <ins> or <del> tags, my standard “pull-quote” div for images, etc), I can seamlessly switch to the HTML view and back, without worrying about the Visual editor messing with my manual edits later.

And for those of you who might wonder, but haven’t seen it mentioned, the new improvements will be filtering into WordPress.com and the WordPress-MU codebase very soon.

ShareThis

• Faster load times.
• Multi-file uploads.
• New “Media Manager” for images, audio, video, etc.
• Built-in gallery function.
• Built-in (and pluggable) Gravatars support.
• New backend design.
• One-click auto-update for plugins.
• Reactivate plugins after a ‘Deactivate All Plugins’ action. (my feature! )

As a long-time WordPress user and developer, the new design for the back-end admin screens threw me at first. I had the same questions that I saw many others post to the mailing lists. “Why did they clump these links together, and move these other ones to a different spot on the page?” But the more I’ve used it, it became obvious that the new menu layout made sense. The most frequently used items are prominent. The less-often needed ones are moved out of the way, but still easily accessible. I’m still not totally thrilled with the color choices (some elements don’t have enough contrast, to my eyes), but it turns out the the admin screen colors are pluggable, as well.

One of the more exciting features (IMO) is the one-click plugin updater. When you see a notification that a new version of a plugin is available, you’ll also see an ‘upgrade automatically’ link. If your server supports all the functions needed, clicking the link will download and install the new version for you. I will note that on my server, this feature does not always work flawlessly, and I’ve sometimes had to quickly download and install a plugin manually to fix a broken plugin. I’ve shared my observations on this, and I hope that they’ll be able to make this feature more robust before final release. My advice is to use this feature with caution for now. But I’m hoping that my problems with it are due to my server, and that I’ll have better luck when I get things moved to my new host.

Overall, I’m liking the new release. I haven’t had a chance to play with the media management and gallery features yet, but I’m looking forward to giving them a try. I think the new admin arrangement will be easier for new users, and I think most established users will come to appreciate it, too (and for those looking for something even more different, there’s the Fluency Admin theme).

As always, when toying with pre-release code, don’t forget to back up your database and files before you upgrade! Give it a spin, kick the tires, and let us know what you think.

ShareThis

I mainly mention this as warning that if my site appears to be down, email bounces, or any other strangeness occurs, it might be because I’m in the middle of moving things around. It will probably be another couple of days before I start shaking things up. While I’m moving thing around, I might try consolidating some of my stand-alone WordPress sites into a WordPress-MU setup. That would make upgrades and other site management tasks a bit easier, I think.

With a little luck, and a lot of attention to detail, you might never know that I’ve changed anything. Yeah, right! Watch this space for further announcements.

ShareThis

If that doesn’t make sense to you, don’t sweat it. You can upgrade and it will work fine (on both older versions of WP and the upcoming version 2.5). Or you can keep the previous version, and it will continue to work fine, too. The only way things would work any different is if you are running WordPress 2.5 (or later, one day), and if you had an additional plugin which defined a new get_avatar() function.

ShareThis

And on that note, I’ll mention that Internet Explorer 8 Beta 1 is available for download. Go break the web!

ShareThis

And since I know lots of people will ask, I checked my plugins, and most of them (HeadMeta, Text Filter Suite, and Easy Gravatars), work just fine. The one that doesn’t work is Theme Preview. When I can find time, I’ll try to figure out why.

The official WP release is slated for March 10.

Update 2008-03-29: Something must have gotten fixed, because my Theme Preview plugin does indeed work in the release version of Wordpress 2.5.

ShareThis

But waitaminnit… What’s this stuff about forward compatibility by adding some new X-UA-Compatible header to my pages or my server? Am I reading this right? Are you telling me that in order for IE8 to use its fully compliant rendering, we have to add something new to our pages? And that if we don’t, it will fall back to rendering pages just like IE7? Is that what this means?

That’s just dumb.

Screw their stupid “don’t break the web” motto. Break it! Break the web in the name of progress! How will we ever move forward if you keep dragging us back? And while you’re at it, quit trying to misdirect us with that “don’t break the web” nonsense. Putting out a browser with excellent CSS support is not “breaking the web”, it’s fixing it! There’s no real shame in putting out a better product, and admitting that the previous versions had flaws. This is a concept called “continuous incremental improvement”.

There has already been a lot of reaction from the web development community. There are several big names behind the idea. There are several big names against it. I’m not a big name, but I fall in the latter camp. This is not “forward compatibility”, it’s not “forward” anything. This is keeping progress of the Internet Explorer browser and adoption of better standards at a crawl instead of letting them make an evolutionary jump.

Oh, and unless I’m missing something here, there was already a mechanism in place that the IE team has already encouraged web developers to use, which could do the same job: conditional comments. What’s that? Oh yeah, there are problems with that, too.

If you need more reading material on this subject, check out Mark Pilgrim’s links. At the time of this writing, he has pointers to 29 articles, and I’m sure there will be more.

ShareThis