We are migrating our site xxx.com to a smaller site in the same domain xxx.com. In this process about 2000 pages are in excess and are to be redirected. We are using DNN 7.4.1 and Advanced URL management.

Many pages do not have a corresponding page in the new site and are to be redirected to home.

Other pages have corresponding pages and should be redirected accordingly.

For instance http://xxx.com/resorts/switzerland/zermatt.aspx should be redirected to http://xxx.com/resorts-monterosa/zermatt

We have tried to do that in the GUI, but it didn’t work. http://xxx.com/resorts/switzerland/zermatt.aspx redirects to the page http://xxx.com/resorts but in the address field the original url http://xxx.com/resorts/switzerland/zermatt.aspx is written.

We figured out that since we have set the value Hide page extensions to true so http://xxx.com/resorts/switzerland/zermatt.aspx is first re-written to http://xxx.com/resorts/switzerland/zermatt so it has to be /resorts/switzerland/Zermatt that has to be entered in the database table TabUrls. We figured that one out ourselves :)

The second question is related to the Seq field. For instance, for a specific page there is already two entries, because that page name has been changed in the past. One status 200 entry and one status 301 entry. The 301 entry has 0 in the field Seq, and the 200 has 1. Using the GUI to add one more 301, because this page is the target of another redirect, shows that one more entry is added in the database with seq 0. So since we want to do this programmatically, we have to increase the Seq field value with one for the existing records for that particular page and then insert the added 301 redirect with Seq = 0. Does anybody have experience from this?

Another issue we stumbled upon. In the new portal we have a page xxx.com/about-us. In the old portal there is a page xxx.com/about-us/contact/emailform.aspx. This url will be re-written to xxx.com/about-us/contact/email. I guess it matches the url form the beginning and when no more pages are found it assumes the rest is the query string? Or? So if you want to have 404’s for an incorrect url how is that achieved? What is the desired behavior anyhow in this kind of situation?

Also, we will have about 1000 urls permanently redirected to home in the new portal. Will this pose a problem? Does one keep these records indefinitely or should they be deleted after some time?

Other fields in the TabUrls table: CultureCode, PoralAliasId, PoralAliasUsage. Is there some documentation?

A few questions but we are grateful for a little guidance.

Best regards