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 ...moving installation from subfolder to root of domainmoving installation from subfolder to root of domain
Previous
 
Next
New Post
3/31/2008 5:53 AM
 

I have installed DNN in a subfolder of my domain, because at first i couldn't get it to work in the root.

But now i want the installation to be in the root of my domain, i don't want to see http://www.domain.com/dnn/default.aspx but www.domain.com/default.aspx

I currently us a frameset to hide the  "dirty" url, but this is not good for search engines.

I tried adding a portal alias:  www.domain.com . the default is www.domain.com/dnn .

copied the files to the root, but then the site won't work.

can anybody help me with this, or point me to a guide or something. Forum search isn't working....

ps. the site has lots of pages and content already and I don't want to lose this. thanks.

 

 
New Post
3/31/2008 8:59 AM
 

playah wrote

copied the files to the root, but then the site won't work.

Man, I hate those "won't work" errors.  Did you try the "Now Works" patch?

Seriously, what "won't work" here?  Did you configure the alias correctly?

Jeff

 
New Post
3/31/2008 12:56 PM
 

The location of the installation has nothing to do with the portal alias.

What matters is the way the server points to the installation location regarding that alias.

Hence, in the first place you could set the server point to the oroiginal folder for the site (the portal alias without /dnn/ addition)

Now, after moving the installation to the new location do the following:

1. change the alias in the DB (just chaneg the text in the portal alias table) to the one you want (I presume you have acces to the DB)

2. Change the pointer in the server for the new name to the new location

Is it localhost?


Yehuda Tiram
AtarimTR
AtarimTR
972-2-5700114   |   972-54-4525492   |    http://www.atarimtr.co.il
 
New Post
4/1/2008 5:03 AM
 

Jeff Cochran wrote

 playah wrote

 

copied the files to the root, but then the site won't work.

Man, I hate those "won't work" errors.  Did you try the "Now Works" patch?

Seriously, what "won't work" here?  Did you configure the alias correctly?

Jeff

LOL.... sorry, but that was from an earlier post:

When I copied the source files to the webserver, I copied them directly in the root of the website. This seemed to cause the error.

When I first created a folder and copied the files in that folder and created a new virtual folder (and created an application from it), the site works fine.

 I looked in the Default.aspx.vb fie and in this section:

           ' error loading skin - load default
            If ctlSkin Is Nothing Then
                ' could not load skin control - load default skin
                If IsAdminSkin(PortalSettings.ActiveTab.IsAdminTab) Then
                    PortalSettings.ActiveTab.SkinSrc = Common.Globals.HostPath & SkinInfo.RootSkin & glbDefaultSkinFolder & glbDefaultAdminSkin
                Else
                    PortalSettings.ActiveTab.SkinSrc = Common.Globals.HostPath & SkinInfo.RootSkin & glbDefaultSkinFolder & glbDefaultSkin
                End If
                ctlSkin = LoadSkin(PortalSettings.ActiveTab.SkinSrc)
            End If

The ctlSkin object was still 'nothing' after the IF. Seems like the variable 'PortalSettings.ActiveTab.SkinSrc', pointed to /Portals/_Default....' and that file could not be loaded.

I checked with my local install (with a virtual folder) and there the variable was:

'/DotnetNuke/Portals/_default/....'

So that was the only difference in the entire install, and obviously was the problem all the time. I think when installing in the root the first / should be removed. So '/Portals/... ' would become 'Portals/...'.

 

 

 
New Post
4/1/2008 5:07 AM
 

Hi,

The location of the installation has nothing to do with the portal alias.

What matters is the way the server points to the installation location regarding that alias.

Hence, in the first place you could set the server point to the oroiginal folder for the site (the portal alias without /dnn/ addition)

I tried to add an extra portal alias. This is the same but without /dnn, so e.g. : mydomain.com/dnn ->add alias mydomain.com.

Or what do you mean by  "set the server to point to", in IIS ? or DNN?

Now, after moving the installation to the new location do the following:

1. change the alias in the DB (just chaneg the text in the portal alias table) to the one you want (I presume you have acces to the DB)

As I added an alias this would be already in the table...? Does this matter?

2. Change the pointer in the server for the new name to the new location

Which pointer do you mean here again? IIS? It is not localhost, mydomain.com , it is on a shared web server.

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...moving installation from subfolder to root of domainmoving installation from subfolder to root of domain


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