Comments on: Improving the 404 Search http://nslog.com/2005/11/14/improving_the_404_search The Weblog of Erik J. Barzeski Sat, 22 Nov 2008 17:23:34 +0000 http://wordpress.org/?v=2.6.3 By: Erik J. Barzeski http://nslog.com/2005/11/14/improving_the_404_search#comment-17405 Erik J. Barzeski Wed, 16 Nov 2005 19:14:35 +0000 http://nslog.com/2005/11/14/improving_the_404_search/#comment-17405 That way didn't work because it's difficult to determine the primary category. Obviously it can be done, but I don't feel like writing the JOINs and whatnot to get it done at this point. That way didn't work because it's difficult to determine the primary category. Obviously it can be done, but I don't feel like writing the JOINs and whatnot to get it done at this point.

]]> By: A View from Home http://nslog.com/2005/11/14/improving_the_404_search#comment-17406 A View from Home Wed, 16 Nov 2005 17:39:13 +0000 http://nslog.com/2005/11/14/improving_the_404_search/#comment-17406 <strong>No more useless “file not found”</strong> I launched this blog in January 2003 and since then have posted over 1100 entries. It's been a learning experience. I've changed the blog's file structure a few times. If you blog and you use a blogging content management system... No more useless “file not found”

I launched this blog in January 2003 and since then have posted over 1100 entries. It's been a learning experience. I've changed the blog's file structure a few times. If you blog and you use a blogging content management system...

]]> By: Erik J. Barzeski http://nslog.com/2005/11/14/improving_the_404_search#comment-17404 Erik J. Barzeski Tue, 15 Nov 2005 20:20:23 +0000 http://nslog.com/2005/11/14/improving_the_404_search/#comment-17404 Bud, that doesn't really solve the problem at all, nor is it something I'll do for several reasons. One of those is that good URLs don't change, so The Sand Trap is not getting a new URL format. Plus, it'd further strain MovableType: if there's no gain, I'll always take the faster (re)build setup. Plus, users can already "back up" a level to find the article. The system works pretty well now and does a pretty good job of helping the user. What it doesn't do is match filenames. I just helped Judi write something that does this, though, so perhaps I'll go that route later on… Basically, it searches for basenames instead of the entry ID (as the NSLog variation does). Bud, that doesn't really solve the problem at all, nor is it something I'll do for several reasons. One of those is that good URLs don't change, so The Sand Trap is not getting a new URL format. Plus, it'd further strain MovableType: if there's no gain, I'll always take the faster (re)build setup. Plus, users can already "back up" a level to find the article.

The system works pretty well now and does a pretty good job of helping the user. What it doesn't do is match filenames. I just helped Judi write something that does this, though, so perhaps I'll go that route later on… Basically, it searches for basenames instead of the entry ID (as the NSLog variation does).

]]> By: Bud Landry http://nslog.com/2005/11/14/improving_the_404_search#comment-17403 Bud Landry Tue, 15 Nov 2005 19:41:41 +0000 http://nslog.com/2005/11/14/improving_the_404_search/#comment-17403 From the surfers point of view, a truncated URL will either pull up a complete URL I have typed before, and that my browser can often autocomplete, or send me a 404 message. The most natural response of a surfer to a 404 message, is to backspace to the last slash in the URL, or back to the domain name if need be, and hope that rung up the ladder in the hierarchy actually resolves to an html file, an actual page, ideally with links to the article one was trying to reach with the broken URL. Which might call for more work from the webmaster. The most common workaround I see would be for the URL to always refer to a level referring to its date of publication. for example http://thesandtrap.com/archives/clubs/sneak_peak_at_taylormades_2006_new_products.php Which wrapped in this comment box by the way, could be called http://thesandtrap.com/archives/clubs/2005/11/11/sneak_peak_at_taylormades_2006_new_products.php Most surfers looking for that article might backtrack to the date, and hope the article is among others posted on that date. From the surfers point of view, a truncated URL will either pull up a complete URL I have typed before, and that my browser can often autocomplete, or send me a 404 message.

The most natural response of a surfer to a 404 message, is to backspace to the last slash in the URL, or back to the domain name if need be, and hope that rung up the ladder in the hierarchy actually resolves to an html file, an actual page, ideally with links to the article one was trying to reach with the broken URL. Which might call for more work from the webmaster.

The most common workaround I see would be for the URL to always refer to a level referring to its date of publication.

for example

http://thesandtrap.com/archives/clubs/sneak_peak_at_taylormades_2006_new_products.php

Which wrapped in this comment box by the way, could be called

http://thesandtrap.com/archives/clubs/2005/11/11/sneak_peak_at_taylormades_2006_new_products.php

Most surfers looking for that article might backtrack to the date, and hope the article is among others posted on that date.

]]>