First the issues:

1) The Human Friendly URL provider seems to get confused as to which portal alias to use.  I have my primary portal alias, and then my ISP has a portal alias defined for me.  It seems like randomly it'll link to the ISPs portal alias instead of the default/primary one.  I'm contemplating deleting my ISPs portal alias to get around this, but I don't want to kill my DNN back door either.

2) Human Friendly URLs seem to work on most pages with the exception of pages where blog entries exist (which is unfortunately, the most important use of the module to me).

3) The Human Friendly URLs really need dashes (-) between words instead of all the letters smashed together.

Last question sort of unrelated to HFURLs.  What's everyone using for a 301 redirect module for DNN?  I've looked at several different modules, and many of them seem to depend on the URL already existing somewhere.  Others won't 301 to a URL outside of your site (crazy, I know).  I'm going to be dumping a third party module soon and it's RSS feed URL will no longer exist on my site.  And that URL isn't display on a module page anywhere.  So I think I need a lower level 301 redirect engine at work.  I've been looking at URLRewriting.NET (http://www.urlrewriting.net/en/Default.aspx)  Anyone have any thoughts about this approach?

Thanks for reading.

Shawn

Mitch,

Thanks for the reply.  I'm not sure why I didn't get a notification for your post as I thought I had notify on.  Anyway, I stumbled across the URLRewriting.Net project myself and have implemented it successfully.  Now all I have to do is figure out all this human friendly URL nonsense ;)

Thanks.

Shawn

Can anyone please comment about how to tweak the HFURLs to accommodate a page called 'foo & bar'?? with the title 'foo & bar'??

I have to have a page on my site shown in this format, and the special character is required for browsers to properly display an ampersand in the menu/title.

The link in my test/dev site shows as http://localhost/fooampbar.aspx

Thank you, Tom