I have temporary sites up and running version 4.3.4 and have tried to rename them to names that I need to use in the real world. When I rename the home site folders the sites no longer can be found. Is there something published some where that tells what needs to be changed  when a sites name is changed.

Thanks
pdqjohnny

I think by reviewing on how a new installation is setup in the Installation guide you will have some clue. I'm not sure whether your setup is on a localmachine or via a webhost . Also I'm not exactly sure what you are renaming here.

If it's the install directory name you have to make sure that you change your virtual directory to point to the new name and be sure that all permissions are set on the new directory as well.

If it's the domain name make sure you have it pointing to the install directory and very importantly must change or add a new portal alias to reflect the new domain.

If this is not clear or I am off-base with what you are trying to do - let me know.

Mike

---

I've never used the starter kit so I can't be sure at this time but I assume that it set up your original dotnetnuke directory with virtual directory and permissions. Moving the directory is almost like setting up a new installation without the starter kit as referenced in the DotNetNuke Installation Guide that comes with the Docs.zip download.

Basically there are a number of steps you must take even when using visual studio or Visual Web Developer. After copying the installation to the new directory you must create a virtual directory in IIS to point to the new installation and make sure it has Read and  Run Scripts permissions. You need to set up your full directory permissions as described in the guide (under ASPNET account for windows 2000 & xp/NETWORK SERVICE account for windows 2003) and ensure you are running under ASP.NET 2.0. Since your database was working ok and not moved also, you do not need to change any settings there or in web.config. As stated in previous post an important item often overelooked is making sure your portal alias is changed or added to the installation to prevent looping back to your original one.

At this point you should be able to open DotNetNuke in Visual Web Developer and run your portal. The database does not have the name of your installation directory (that is contained in your virtual directory) but does contain the portal alias which is what you type into your address bar - http://localhost/dotnetnuke.

Mike

---