Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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 ...help with running locallyhelp with running locally
Previous
 
Next
New Post
1/9/2007 12:50 PM
 

When I run my solution locally (F5 in Visual Studio), my url looks normal at first:

http://localhost:portNumber/MyWebSite/

but before the browser loads, the url is pointing to a production server (the url changes). Any ideas what causes this?

 

 
New Post
1/9/2007 5:11 PM
 
are you by any chance using the same database for your local copy as for your production server? If so, you need to add a portal alias that corresponds to your local host. Also, you might want to use IIS instead of the webserver that comes with VS2005. Using portnumbers has some small issues still i think

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/10/2007 9:08 AM
 

I restored the production databases to my local machine.

Where do I find instructions for how to add a portal alias? I'm new to DNN and haven't figured out how to start learning. I bought Professional DotNetNuke 4 but I don't see how to add a portal alias.

 
New Post
1/12/2007 4:32 AM
 
well.. the easiest thing to do is to add the new portal alias prior to moving the site and database to another location. If that is not possible, just open the database, open the PortalAlias table and manually add a new alias for your portal

Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
1/22/2007 10:16 PM
 
I am having the exact same issue as the original poster, eg I restored a backup of my live DB on my dev machine. I then changed portal alias ID 1 (Portal 0, no other portals) to be "localhost\virtdir" and have removed all other portal aliases. I changed the web.config so that the sitesqlserver point to this restored, local DB.
When I bring up the site it still re-directs to the live site and the IIS log shows a 302 (redirect).

My first try was just adding an extra alias but it did not work either. IIS is oberating OK, as I can enter an URL say http://localhost/virtdir/403-3.gif and the standard  pic displays.

I then stopped my production server and DNN redirected to the default instance on that server. Weird!!

Anyone got any hits?

Thanks in advance
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...help with running locallyhelp with running locally


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out