Hey Joe, I went through the tutorials step by step and created a new parent portal and it worked great. my new parent portal site floridachads.com. I guess my last hurdle is setting up a parent portal while a web site is still up. For instance, I have www.swanpump.com that must remain up while I am developing the DNN version of it. However, when I create it as a parent portal it takes me to the live site and I have no way of working with the site in a portal atmosphere. I temporarly set up an alias for it that reads dnn.swanpump.com but no matter what I do it just will not go to it. Any thoughts?

Thanks
Peter

OK after going through the working with portal aliases tutorial and I think i have the answer. I create a child portal called swanpump and when I am ready to go live, transfer it to a parent portal. Correct?

Thanks

Peter

Yes, but you really don't need to make it a parent portal to go live.  All that you need to do is to point the live domain URL to the child portal (and modify the portalalias table to also include the domain name).

Hey Joe and Lee, Yes I am working on my site www.jacksonnjgop.com and I will put it up for review in the next week or so. I would also HIGHLY RECOMMEND to anyone starting out, to learn the DotNetNuke "lingo" so they can better understand the issues. I think that was part of my original problem. Understanding child/parent and the relationships. However reads through this and gets down this far, my recommendation (from going through it) watch the video's at least 3 times.

The first time just to get the idea across.
The second time to get the understanding.
And the third time DO as you Watch. (this part helped me understand the most)

Watch, Pause, Do and learn.. Have Fun and make great sites.
Thanks again guys.