Hello,

I need to setup a sandbox version of our live site in order to test a new skin we will be working with, among other things.  Is this possible to do on the same server that the live site is on?  How would I go about doing this?  We tried copying the current live site, and also the database, utilizing a sandbox. subdomain, but our redirects ended up redirecting back to the live site.  I was wondering if you guys/gals had any suggestions?

Thanks,
Kenny

We currently do have a portal alias setup as sandbox.namescape.com. However, the 301 redirects that are setup, also get copied over to the sandbox site, and that is what is causing it to redirect back to our main site. Do I need to disable the redirects before I make a copy of our live site, and then once the copy has been completed, then turn them back on? Or can I just turn them off on the sandbox site? Also, my colleague told me that it is possible the redirects could be stored in the database as well. Does that sound like it could be the case? Thanks, Kenny

DotNetNuke doesn't care how the request get's to it, just that at the point it does the URL that is requested exists as a valid portal alias. If it does it serves up the relevant portal, if it doesn't it serves up the first (default) portal - IMO this is what you're seeing. If you have a module changing a request url to another then that url will be what DotNetNuke sees on the 2nd request and hence the "original" portal loads. I'm not sure what you mean by "redirect module" if youre running a 3rd party product it might be an idea to remove it in your staging/test environment.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US