Last post May 26, 2005 04:05 PM by SDodds
May 26, 2005 10:41 AM|tmichaels|LINK
May 26, 2005 04:05 PM|SDodds|LINK
Excuse mammoth reply..
Dotnetnuke allows you to provide all that you need from a single installation, application and a single database.
Some considerations tho
To set up another portal with your current installation heres what I did..
Create a child portal on your development machine...
You can add roles, tabs and content, I would suggest start by just using core modules
Note, if the portal is only going to be accessed by
www.mydomain.com/mynewportal/ then adding a pointer is not necessary
In effect this is a child portal but if you wish to promote it to a portal pure (parent) then a pointer is required..
Back to dev machine
Under host>portals> export template section
-Select your new child portal to export
-Give it a name
-Give it a description
-The template is placed under portals/_default/
-Copy the template and it resource file
-FTP those files to portals/_default/ on your remote server
Perhaps back up your database :)
-Login as host on your live site,
-Create a new child portal, append mynewportal to the path dotnetnuke generates
-Select your new template
-Assign an adminisitrator
-Visit www.mydomain.com/mynewportal/ ....portal should load
-Login as the admin you created above, configure as you see fit but is everything working ok?, links may need fixing.
-Login as host and add... mynewportal.mydomain.com and/or mynewdomain.com to the portals alias list
Thats it, basically youve created a child portal and promoted it to a parent, I have had no success creating a parent portal from scratch. If your promoting the portal to a parent and are comfortable doing so you can remove the localhost/mydomain/mynewportal
alias and the mynewportal folder created during child setup.
I hope I havnt missed anything vital out, please heed this advice at you own discretion. :)