Hi Josh,

In web.config, go to the friendlyurl provider, and add  urlformat="HumanFriendly" after the regexMatch element, so that your statement looks like this:

<add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlformat="HumanFriendly" />
 

Or have I misunderstood what you are tring to achieve?

dmeiser-
Even considering how much of an improvement as "Human-Friendly" URLs are over standard DNN URLs, be cautious if enabling "human friendly" URLs for an already-established site.  The HF option has had various small issues (well, small until they affect you) right up through DNN 4.9.  This is probably one reason why the option has not been made the default (yet).

I believe things are more stable, now, but there is one issue you'll want to be aware of:  "bad" page names created in DNN versions prior to 4.9...
 
   DNN4774 (also DNN6306) -- Some page names cause failure to render page under HF option.
   http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=4774&PROJID=2

   DNN6597 (also DNN8420) -- Two pages with same name at same menu level result in 2nd page being inaccessible under HF.
   http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6597&PROJID=2

Both items above have been address with a fix in 4.9 that now prevents you from creating DNN pages with names that will cause problems under the HF option.  Unfortunately, if you created pages with "bad" names in a version prior to 4.9 and then upgraded to 4.9.x (or 5.x) you may still run into problems if you enable the HF option.

Also, I have run into third-party modules that broke when using the HF option (though this was the fault of the modules rather than DNN).

 
FYI -- One other issue with the "HF" option that was recently fixed (4.9):

DNN7925:  HF option incorrectly returns fully-qulified URL instead of relative URL.
http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=7925&PROJID=2

 
-mamlin

mamlin:

Thanks for the Heads Up.  I'm using DNN5 and haven't run across any issues just yet.