We have recently created a new DotNetNuke 5.6.1 website to replace an existing DotNetNuke 4.9 website.  Some of our clients had bookmarked various pages on the site (i.e.: www.website.com/Default.aspx?TabId=57), which used to be a custom page that we had created. 

After pushing the new DotNetNuke 5.6.1 website live, clients that now try to hit that bookmarked page are being redirected to the DotNetNuke Login page because the page with a TabId of 57 in the new site is the "Site Log".  They then try to log in, but they don't have logins as the site doesn't require one.  Is there any way to prevent the redirection to the login page and instead just redirect to the home page?

Thanks!

UrlMaster by www.ifinity.com.au has a UI for defining all kinds of redirects.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Jeremy, it sounds like you guys actually built a fresh site from the ground up instead of upgrading an existing site?  This is the challenge with that approach, precisely because the tabid's are system generated and therefore all different when you recreate a site.

You might want to do some proactive analysis of the tabid's associated with other pages in the site... just to try and understand where any other old links might be going to pages that not those intended.  If the business concern merits trying to recover those old tabid's, it could be done manually... just need to figure if the effort is worth the result.  I'd run some reports on the tab names / id's from the old and new and see if anything jumps out at you.

Cheers,
Scott

---

Scott Willhite, Co-Founder DNN