Hello,

I need technical advice for DotNetNuke live portal, As per client requirements URL in the format of friendly and Human readable (Without tabID/PortalID) with .HTM Extensions of page required to implement for SEO ranking.

Below two links helped me to make clear things,

http://www.ifinity.com.au/Blog/Tech...er-Module/

http://www.ventrian.com/Resources/P...yUrls.aspx

I tried Friendly Url Settings from DNN but still searching a mechanism thru which I can show .HTM extensions to my DNN pages/Tabs. I tried to write RegEx with defining new RewriterRule but its giving me 404 Error generates.

Error Image file attached: Url Rewrite for HTM Extension.jpg

Thanks in advance.

Regards,

Jitendra Parmar

Hello,

Most people recommend using the ifinity friendly URL provider

Thanks,

I see a lot of recommendations for iFinity, which I have never seen, but I have to ask... Is the friendly URL functionality that comes with DNN useless?

Is there any useful Url Rewriting that can be accomplished with it?

The URL rewriter that comes with DotNetNuke is not useless.  And, yes you can do rewriting.

URL Master has many more options.

That's good to know.

I have attempted to use it with no results at all. Do you have an example of how I can use it or know of a resource that shows even the most basic usage of this functionality?

Thanks

First time poster; DotNetNewbie; all Google searches for DNN issues seem to lead me here!

My apologies for jumping in, but I do not know if my question is going to be related to Jitendra's or not. I am not sure if my question is related to Friendly URL's or not. I have a hosting account with GoDaddy. I performed a manual installation of DNN 5.1.4 into a directory named "DNN", and created the IIS entry to match it. I created a default portal, "www.domain1.com". Portal alias's are "www.domain1.com" and "www.domain1.com/dnn". This all works fine, but as soon as someone clicks a link, the URL changes from "www.domain1.com/default.aspx" to "www.domain1.com/dnn/default.aspx". I created a second portal (parent), "www.2domain.com", and the portal alias is "www.2domain.com/dnn"...it does not work without the "dnn" at the end.

How can I make the "/dnn" directory not appear in the URLS? I have played with the web.config to no avail. Playing in-depth with DNN has taken it all out of me and it's all running together now. Am I missing something simple, do I need a module, or it that just the nature of the beast?

The way that you get rid of the need to attach the directory name is to use DNS to specify a domain name for the other portal.

Thanks for the quick response Joseph! I'm not sure if I'm understanding your meaning, though. My DNS points each domain to the correct location, and when a visitor initally visits the site, the URL does NOT contain the /DNN directory. It is not until a link is clicked that the /DNN shows up. It's really just an annoyance, I just wanted to try to make that go away. Are you saying that there is some entry that I can make in the DNS for each individual domain that makes the /DNN not show up?

DNS should point each domain at the root directory for your DNN install.

Within DNN, you should have "portal aliases" configured that also associates each domain with the correct portal.

IIS also needs to be configured to point the domain at the root directory.

Rob : The standard DNN Url Rewriter will allow custom rewriting rules (through the siteurls.config file), if you want to do those. The problem is it doesn't give you any scope to change the generation of the Friendly urls, or to redirect existing urls if you change the Url scheme for your site. If you want to do anything more advanced, such as changing the site extension (as suggested by the OP), redirecting Urls and generally changing things around, the standard Url Rewriter doesn't have the capability.

Thanks, Bruce!

(It's good to know that you are watching us here!)