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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving copy of site to another serverMoving copy of site to another server
Previous
 
Next
New Post
8/17/2014 6:45 PM
 

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

 
New Post
8/18/2014 4:38 AM
 
Menu links should point to local pages, but there may be links in the skin with hardcoded paths.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/18/2014 8:51 AM
 
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
 
New Post
9/8/2014 3:54 PM
 
While we are all here, and so I don't reinvent the wheel, so to speak, I need to move several DNN sites, where can I get comprehensive instructions for that? I need to change web hosting companies. Thanks.

Beth Vest
 
New Post
9/8/2014 4:17 PM
 
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)
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving copy of site to another serverMoving copy of site to another server


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.