When I set up a parent portal in a sub-domain, My host adds a folder with that name. However, when I add the parent portal, the only thing I see happen is, the portal name (example: new.domain.com) is added to the portals list and a portals forder with graphic files and a css file is added to the portals directory. Nothing is added to the sub-domain folder provided by my hosting provider and I am unable to access the http://new.domain.com portal. I get this error message:

(The website declined to show this webpage                      HTTP 403

Most likely cause: This website requires you to log in.

"This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.")


I think this is becaues there is nothing in the sub-domain folder. Am I suppose to add a freash copy of DotNetNuke to that folder myself, manually?

Any help would be greatly appreciated.

Tim

When you set up a second domain for another portal to be handled by your DotNetNuke installation, you want that new domain name to be pointed at your CURRENT web directory, not a new one. So, you'll need to work with the tools provided by your hosting provider or ask your hosting provider to help you set this up.

Suppose that you have an existing site, mywebsite.com, and that it is pointed at a web directory called myhttpdocs.

If you want to add another website myotherwebsite.com, you'll also want it's web directory to be myhttpdocs, because that is where your DotNetNuke installation is located.

What actually happens is that DotNetNuke grabs the incoming requests and decides which of your portals should receive each request.

Again, you don't need a new folder, and you don't need a new website. You need to have the new domain name point to your new website. And, of course, you must configure your new portal to have that domain name.

I hope this helps.

Thank you very much,

That cleared away the confusion I had. Everything is working find now...

Can you ask lee Sykes to include this information in his portal video series?

Thanks again,

Tim

I'm sure that Lee is watching!

Besides Lee's superb tutorials -- look particularly at the basic ones for insight on the workings of DotNetNuke -- I've found the "Professional DotNetNuke" book by Shaun Walker, et. al. to be very useful. It's several versions out of date, but the basics still apply. The chapters on site and portal management are very useful.

Hello,

Yes I am watching! - We do discuss in the videos pointing several domains to the same DNN installation folder for multiple portals. You may also want to check out the tutorial here:

Lee, Thanks for you reply...

You did an excellent job with those portal videos. They Helped me alot.

I just haven't seen any things stating explicitly that, a parent portal's creation is done all internally.

The problem arised for me when my hosting company added a folder with the name of the subdomain to my wwwroot. That got me to thinking, "where does the home page's default.aspx file go for a parent portal? How is the main page and additional pages actually created? Is there something wrong with my install?(think that a parent portal was actually a fresh install of all dnn install files in a different location."

I could not find any information in the dnn documentation that actually addressed portal creation code wise.

Coming from a Naval Aviation Maintenance Background, I guess I was just thinking too much into it.

Know I know It was just a portal Id and Alias issue, all done behind the scenes..., less work for me :-)

Such is the life of a Padawan learner - new programmer...

If you're serious about DotNetNuke, IMHO "Professional DotNetNuke 4" should be on your bookshelf. It's dated (as it's over a year old), but the basics haven't changed at all!