I need to configure a community 6 version of DNN site to a developer server; in doing so the front page looks fine, but clicking on links on the front page to go inside , the links lead back to the old site on the old server. The sql database has been restored from the old site to the new development  server. What is the best way to continue this process on the development server>
Ed

Most likely you need to hack the portalalias table to include the url you are now accessing the site from. Absent that; it may have decided to use the old portalalias row. Then it's not unusual for a page to come up, but the system generated links, based on the old portalalias point back to the live site.

As Sebastian points out; skins and user generated content may have hard coded links back to the live site.

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

Beth,

It seems that you have mastered the basics. Likely, your issues have to do either with hard-coded links (as Sebastian indicated) to that the site is set to redirect to the old URL For the latter, you can fix this from Site Settings before you move (disable redirection and remove the designation of the primary URL).

For efficiency, you might find it useful to purchase a copy Evotiva's DNN Backup module. If you are working on multiple sites, you may want to purchase a license that is valid for multiple domains.

But, as you are switching hosting providers, you might find that your new hosting provider will be extremely helpful in moving your sites. Depending, you might avail yourself of their site moving service (I believe that there are several hosing organizations that provide this service.)

If you need to correct hard-coded links in the site contents, Engage's F3 Module (it's free and on Codeplex) might be helpful.

---

Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)