I typically do all my coding in a development sandbox, but with wordpress I was having trouble with the url settings. My local development environment had a url of http://dev/gh, but the public url is greghostetler.com. So once I changed the url in the wordpress wp-options table I could no longer access my local environment, because it would redirect to the public url.

The url in the options table can be overridden in the wp-config file on my dev environment.

define('WP_SITEURL', 'http://dev/gh');

Firefox(+Camino), Safari, and Opera:

These browsers are easy to setup and only require a 16×16 image file (png, jpg, or gif) and a link tag in the head tag of your code.

<link rel="icon" type="image/png" href="/favicon.png" />

IE7:

IE 7 is a little more tricky. First, IE requires an actual icon file. Not just a jpg or png renamed with an ico extension. But no worries there are a few sites online that will convert your images into ico format for you.

IE automaticaly checks the root directory for a file called favicon.ico, so thats where I recommend placing your image. (/favicon.ico)

You don’t need any link code snippet to make this work, but if you wanted to force IE to find it and or change it for another page you can use the following link code in the head tag.

<link href="/favicon.ico" type="image/x-icon" rel="shortcut icon" />

I wrap this code with an IE conditional comment. Although the other browsers recognize this code, it’s not correct if your trying to produce accurate XHTML, because of the space in “shortcut icon”.

<!--[if IE]>
	<link href="/favicon.ico" type="image/x-icon" rel="shortcut icon" />
<![endif]-->

Troubleshooting IE:

If your favicon doesn’t show up immediatly it’s because you need to clear your temporary files as well as your browser history. That should force IE to update the favicon.

Also make sure that your not preventing IE from cacheing your favicon. You’ll need to check your headers, using a tool like fiddler. But most likely you won’t need to worry about this.

If you have any questions don’t hesitate to drop me an email.

Currently I live right on the edge of 3G coverage, I was surprised to see that I even was able to get 3G c

overage considering I live in the middle of nowhere. I’m about 20 min from Columbus OH.

My broadband connection is wireless and it caps me at 185 kilobytes per second.

The app I used for the test was Speedtest[itunes].

Ignoring directories in git was a concept hard for me to grasp. The gitignore help file didn’t help me all that much.

If the pattern ends with a slash, it is removed for the purpose of the following description, but it would only find a match with a directory. In other words, foo/ will match a directory foo and paths underneath it, but will not match a regular file or a symbolic link foo (this is consistent with the way how pathspec works in general in git).

This never worked for me. The only way I could get it to work was to use something like “directory/*” in my .gitignore file. I could also just use “directory”, but that would match any file and directory with that name. It would also look for other matches further down the tree recursively.

So in summary to hide the build directory use:

build/*

Since it’s launch in late 2007, I’ve been buying all of my MP3′s from Amazon. It was a pretty easy decision for me to make, no DRM, acutal MP3s, a higher bitrate (256), and it’s cross platform. But there is still room for improvement.

Read the rest of this entry »