Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...redirecting to another urlredirecting to another url
Previous
 
Next
New Post
10/30/2008 10:47 AM
 

Hello all.

We have a DNN installation with several portals.  On one portal the client wants us to "point" the old urls, www.oldsite.com/contact.html to a page on the new dnn site.  I know exactly how I would go about this if the site was on its own installation, i could pretty much just set this up in IIS, by adding a dummy contact.html file in the dnn root, and configure IIS to redirect this to the corresponding page on the DNN site.  Since this site is on an istallation with a other sites on it, I dont think I can do it this way.  My concern is, lets say www.anothersite.com is also on this DNN installation.  If I do it that way, then www.oldsite.com/contact.html and www.anothersite.com/contact.html would both go to the site I set up the forwarding for www.oldsite.com.  Now I realize that the chances of people blinding appending /contact.html to the end of any random url that is on this installation is pretty low, but if there is a better way of getting the end result that I need, I want to do it the right way.  I have tried playing around with Friendly URL Settings, but I have made no headway so far.  This tells me, A - the friendly url rewrite, does not do redirection or, my regular expression is incorrect.

My match expression currently is *./contact.html and my replace with is ~/Home/tabid/3935/Default.aspx

So.... 2 questions

1-Can Friendly Urly settings be used in the way that I describe above
2-What is the right way of accomplishing the behaviour above

Thanks in advance

 
New Post
10/30/2008 3:21 PM
 
  1. Native DNN Friendly Url implementation won't do redirects.
  2. iFinity's Url Master lets you map old Urls to new Urls via a config file.

Tom Kraak
SEO Analyst
R2integrated
 
New Post
10/30/2008 3:46 PM
 

Thanks so much for the info!  We will take a look at this module.  Is it pretty easy to set up?

 
New Post
11/2/2008 12:17 AM
 

Hi Brian

I'm the author of the Url Master module that was suggested to you.  With this module, you have two choices to go from your 'old' site to your new site.

1) You can just setup the DNN pages to match your 'old' site pages.  For example, contact.htm -> you'd create a DNN page called 'contact'.  You would then set the Url Master module to use '.htm' for the site extension, and the old urls would just work as you'd expect.  Note that you'd have to do a 1:1 mapping of old urls to new DNN pages.  In this case, there's no redirect, you're just setting up your new site to use the old urls.

2) You can redirect the old urls to their new equivalents.  For your 'contacts.htm' example, you'd pick the page you'd like the contacts to go to (for example, 'Contact Us').  Then you'd go to the 'page urls' page that the Url Master module installs on your site, and in that page you'd select the 'new' page (contact us) and enter in the 'old' url (contact.htm).  Save the changes, and now, when you request 'contact.htm' you will get 301 redirected to 'contact-us.aspx'.

Note that in both cases you'll have to map the .htm variable to the ASP.NET extension in the IIS configuration, so that ASP.NET responds to a .htm request.  You'll also have to modify the standard Url Master regex to remove \.htm and \,html from the 'ignore Regex' field (normally the module ignores the .htm requests)

You can download a free trial and setup your site from http://www.ifinity.com.au/products/Url_Master_DNN_SEO_Urls/ - you should be able to get the redirects going in about 10 or so minutes.

regards

Bruce

 
New Post
11/4/2009 11:27 AM
 

Hi Bruce,

You said that, "in both cases you'll have to map the .htm variable to the ASP.NET extension in the IIS configuration, so that ASP.NET responds to a .htm request. ".

I'm running in a Shared Hosting environment.  Can I still make this change to the IIS configuration?  In a normal scenario how would I go about doing that? 

Thanks,

Walt

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...redirecting to another urlredirecting to another url


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out