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 ...From localhost to actual siteFrom localhost to actual site
Previous
 
Next
New Post
11/9/2007 3:22 AM
 

Hi there

I have (finnaly) maganged to get my DNN 4.6.2 installation working. I have installed it locally... After installation I have uploaded all generated files to the actual www site.

My problem now is that the DNN installation (probably the DB) remembers that the initial installation originates from localhost. So when I acces the www site, I am redirected to localhost :-) Greate...

So : Could anyone please tell me where I change the base url for the site - change localhost to www...

(By the way : I really like this product :-))

 
New Post
11/9/2007 3:32 AM
 

Hi,

You need to add a Portal Alias for your new location. It can be changed when you log in as a host on the Portal Settings page (all the way down the bottom).

Or, if you need to do it on your production database: edit it directlyinto the PortalAlias table.

Hope this helps.


Web applications, DNN websites, modules, skins and support
 
New Post
11/9/2007 6:20 AM
 

Hi Stefan

I'll do that. I still have access to the user interface from my localhost, so I suppose I can just add the portal alias from there.
Does this give me the ability to work on DNN from localhost (create sinks and modules locally etc) and then upload them to the production DNN without any changes to web.config etc.

 
New Post
11/9/2007 7:09 AM
 

Yes, just make sure you add the new alias and don't remove the localhost one.

You can more-or-less just copy the whole site over to you live environment and maybe only change the connectionstring in web.config.

Skins might also need parsing by the way, but you'll notice that because of missing images and stuff like that.


Web applications, DNN websites, modules, skins and support
 
New Post
11/9/2007 1:25 PM
 

Hi Stefan

I did what you suggested. I added a portal alias to the single portal that I have defined (the one that came out of the box with the installation).
I now have two aliases : localhost and www.[mysitename].com

When I try to access www.[mysitename].com I am still redirected to localhost...

What have I done wrong?

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...From localhost to actual siteFrom localhost to actual site


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