Look alive there folks, WordPress has released an update to their web publishing platform.  Version 2.8.1 is live and it seems like a quick and easy upgrade.  In case you haven’t tried WordPress lately (or at all), or haven’t upgraded in a few versions, they now have built in the capability to upgrade not only plugins, but also the whole distro right through the point and click admin panel or dahsboard.  You need an FTP account somewhere to make the magic happen, but most people running a web site have that, and if not they are easy to come by.  So far, I have had great success with their automatic upgrade features, both for plugins and WordPress itself.  Being who I am I was very skeptical at first, but it’s actually worked wonderfully so I thought I would share.  Now, get out there and get to upgrading.  Unlike some other software entities that add more bugs and security holes than they fix, the guys and gals at WordPress actually imrpove the software with each new release.  Let me know what you think, post a comment and share your opinion.

I just ran into an interesting little ripple in WordPress when trying to create a new page using a template.  The problem was that I had no option to choose a template, it just wasn’t there at all.  Took some cypherin’ on Google, but I found it.  It was my theme.  I switched to the default theme and there it was.  I picked my template and then switched my theme back.  Hope this helps!

Description and Problem:

Google Gears is a plug-in that extends your browser to create a richer platform for web applications. There are many Web applications that currently make use of Google Gears. Some of these include Google Docs, Google Reader, MySpace, Picasa, Zoho and (the reason for this post) now even WordPress. Google Gears, or simply just Gears as it is now known, not only enables offline browsing of supported sites, but it can also greatly improve the performance of these sites and web applications like WordPress. This makes working with supported web applications much nicer.

Now, my problem (and many others of you out there) has been that I am running 64-bit Ubuntu (8.04 Hardy Heron) and Google has not made a 64-bit version of their Gears software. They cite lack of time and testing resources, but my guess is it’s not that important to them since there probably aren’t too many 64-bit users out there. Luckilly for us, Gears is an open source project. This is now a prime example of the beauty of open source software, in that some really smart people created an “unofficial” patch that allows you to install and run Gears on 64-bit Linux in Firefox. In my case it’s Ubuntu and Firefox 3.x, but I have read folk that have had success with SuSE and others as well. It only took me about five minutes once I found the patch.

Here are the steps I took to get this installed, up and running:

Grab the latest version of the Gears binary that has been patched for 64bit at http://www-personal.umich.edu/~swolchok/gears/, I used this command:

wget http://www-personal.umich.edu/~swolchok/gears/gears-linux-opt-0.4.9.0.xpi

Open Firefox and choose File->Open File and browse to where you saved the file you just downloaded. It should open an install window, you want to press the “Install Now” button to start the install.

Once the install is complete, press the “Restart Firefox” button to restart Firefox and complete the installation.

Summary:

For me, upon the initial restart, I got an error about this addon not being compatible with my architecture. Despite that it seems to work fine, and I haven’t gotten any more errors since then, so I would suggest you simply ignore that error.

Lastly, go to a site that is supported, add it to Gears and enjoy! If you have any questions or comments, post ‘em below.

I wanted to write up something about the latest WordPress release, version 2.5. I have updated all of the WordPress powered sites that I manage which is more than ten and the upgrade went flawlessly on all sites. Each upgrade was the same, no variances. Why do I mention this part of the process? Well, because I have seen many instances (*cough*Win*cough*dows*cough*) where the same upgrade went very differently (and sometimes even failed) on different computers, even though they had been built or imaged or the application installed off of the same baseline. So, when I can install all of the WordPress upgrades and every one of them not only works, but operates as expected, that’s a big deal to me. This has been the norm in the past as well, not just in this last upgrade. Read the rest of this entry »

If you haven’t ever used WordPress for your website or blog, you don’t know what you are missing. I have used almost every CMS out there, including PHP-Nuke, Post-Nuke, e107, PHPWebsite, CPG to just name a few of the more popular ones. However, once WordPress got past the 2.0 versions, it was all over. I love the WordPress platform and use it for many different websites that I manage. I do sometimes run something other than WordPress if I have some specific need that something else does better, but for a good, solid blog and/or website platform I find it hard to beat WordPress.

That being said, one thing I have seen people have trouble with is Permalinks. This is when you change the link structure from the default style like this:

http://example.com/?page_id=N

to something more visually appealing like this:

http://example.com/category/post-name/

or

http://example.com/year/month/day/post-name

The friendly Permalink option is not only easier on your visitors, but it’s easier for search engines as well to index your site. That means that setting Permalinks to something friendly is a good idea on many fronts. You can set the Permalink style in the WordPress admin panel under Options. However, when you do that you also have to update your .htaccess file (on Apache) in order to process the links properly. I have included below a nice .htaccess snippet that you can drop in to get your Permalinks working, check it out:

# BEGIN WordPress Permalink Rules
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress Permalink Rules

I hope that will help in your Permalink adventures!