First, I want to say I think it really sucks to not be able to install in the root directory anymore! GoDaddy isn't the only one doing that. My hosting account is the same way. It was real easy to add subdomains and parent portals when the main domain was set up in the root directory. Now it is all a pain.

A bit of advice on installing...create a folder that looks "natural" to the site. For example, my personal site is denelwardell.com. I created a folder called "dw" to install the dnn app in. So, my website is actually denelwardell.com/dw. Now, when I add pages, such as "About Me", what comes up is denelwardell.com/dw/AboutMe.aspx. The "dw" is barely noticeable. You can even make that folder for your installation just be one letter or one number.

Something else I wanted to mention is the forward with masking that was suggested. This is sometimes a problem with IE. I have a client that has all the domain extensions for his domain, you know .com, .org, .net, .info...etc. He wanted everyone to only see .com, but because of his previous web designer, and their hosting company, we couldn't get the .com released to us in order to set the original site up on that extension. So, I tried the forward with masking. The only problem I saw with it at first was that he could not send anyone directly to a specific page on his site by just giving them the link using the .com. But he was ok with that.

Where the real trouble came was when he started getting a lot of clients registering with Internet Explorer. His clients would log in, then go to a restricted page, that they should have access to, and it would bring up the login page again. I had no idea what was causing the problem. I could not re-create the issue. On my computer, I use Firefox. I just happened to figure it out when using Internet Explorer on my hubby's computer. I logged into his site with the SuperUser account, and when I went to a restricted page, it redirected me to a login page. It donned on me that all the people that were having this problem were using IE. Even then, though, I did not realize it was the masking in conjunction with IE until I went to the actual domain, logged in, and had no problem navigating while staying logged in. IE was really messing up the member pages with the forwarding with masking. It was not acknowledging logins on all the pages once the member was logged in. I almost lost my client over this, because he was losing clients who were getting quite frustrated.

Obviously that is an IE issue, and not DNN's or any of the hosting companies. However, if we were able to install in the root directories again, I bet that would alleviate a lot of those kinds of issues.

Just my two pence worth.

hi there!

I am really having problems and it shouldn't be!
Are you actually using godaddy with a subdomain or are you using a new domain under your primary hosting account?
The reason i ask is because i am still having problems getting a new "parent" portal to function with a subdomain. 
So much time has been wasted!!!

Can someone please let me know what is/needs to be physically in a new portal directory?  And, do I need to alter any configuration files on the site itself?

My dnn dir is “/wg”.  am using dnn 6.0.0.0

>The smart thing to do on GoDaddy is to Forward and Mask PerfectDomain.com to Root.com/DNN/Child, and everything behaves like magic

I've done this under the godaddy setup prior to creating the new portal in dnn:
1. HOSTING DASHBOARD - DOMAIN MANAGAEMENT - ADD SUBDOMAIN
    create/manage subdomain “tnpc” located in /wg/tnpc   (i have also tried just "/wg" and "/tnpc" in additional attempts)
2.  DOMAIN MANAGER
    subdomain tnpc.nwg.com forwarded to www.nwg.com/wg/tnpc  
    (i have also tried forwarding to www.nwg.com/wg which brings me to my default install and it won't recognize the new administrator)

In dnn the create new portal:
 portal type – parent
 portal alias – tnpc.nwg.com
 home dir - /tnpc      (btw, I also tried /wg/tnpc which it didn't like and i tried just leaving this field alone)
 title – test npc
 descr – test npc 
 keywords - blank
 template – default website

in the in the new parent portal subdirectory (/wg/tnpc) just after creation are these files:   
/cache  
/images
/templates
/users
logo.png
portal.css

>Last I recall checking, this applied to subdomains as well so for all to work you would need
>Child.Root.com,
>Child.Root.com/DNN and
>Child.Root.com/DNN/Child as portal aliases, in addition to
>Root.com/DNN/Child.

Once the portal is in place, I did add all aliases as referenced so that the portal alias list is:
tnpc.nwg.com
tnpc.nwg.com/wg
tnpc.nwg.com/wg/tnpc      (this one is forwarded)
nwg.com/wg/tnpc

note that it -dnn- will not accept "nwg.com/wg" as a portal alias - the update just sits there for hours...

just for kicks have also tried in another attempt:
tnpc.nwg.com
tnpc.nwg.com/tnpc
tnpc.nwg.com/wg
nwg.com/tnpc

i think i am using the right definition for "parent" and this is a "parent" portal and not a "child" portal - would you please confirm?
i have really tried all the premuations i can think of and for the amount of hours spent am getting really behind and this can't be right!
any help is appreciated!  thanks!

-gtb