How to change the DotNetNuke Install Directory Folder name for a Godaddy Economy Hosting website – 2

Posted on by

Part 2 How to Change the DotNetNuke Install directory folder name for a Godaddy Economy Hosting Website. OK so now we are fully backed up with the DotNetNuke install folder and a fresh copy of the database. Now we are ready to take the next steps. It is my opinion that the install folder and the database work independently of each other, and the folder name is not as important as thought. The web.config file has not been changed, only copied. So any of the keys, or database names all remain the same. The only things that have been changed so far are:

  1. New portal alias created in the DotNetNuke portal.
  2. a fresh backup of the install folder in the FTP File Manager, (separate and untouched)
  3. a fresh backup of the database in the _db_backups folder,
  4. a new folder in the IIS Management or Godaddy Virtual Directory of your desired new folder name,
  5. and a new folder in FTP File Manager with the exact same name as the new one created in IIS, with fresh copies of all files in the original DotNetNuke installation.

Items 2 and 3 above can all be brought back and everything the way it was if something messes up. With this method everything can be turned back.

Now it is time to change some things around.

  1. Log into the Godaddy FTP File Manager.
  2. In the root directory find the welcome.html file.
  3. Click the box next to it and press “edit” at the top.
  4. if it comes up in its structured format, press the “Html” button to see the code.
  5. towards the top find the line that reads-  < script > { window . location = ‘http://www.yourdomainname.com/dotnetnuke’ } < / script >
    (minus all the spaces) where it says /dotnetnuke is where your current undesirable directory name is. The best thing to do is put a “< ! – -” before the opening and a “- – >” (again, minus the spaces and the quotation marks) after the closing script tags, this way you always have the original, just in case a character gets misplaced.
  6. Now that you have the script command line isolated, copy and paste it right underneath of the original. Make sure this one does not have the “html disregard” tags around it.
  7. Change the new line directory name to your new directory name that you set up in the first part, at IIS and FTP.
  8. Save or press OK and save in the next frame. Close the frame and it should load.
  9. You should now be able to type in the domain name in your browser and it will load the new folder name.

There may be a few things you need to know.

  1. You may have to wait up to 24 hours before the new virtual directory will take effect. It may not come up immediately like the domain manager will point to it. It will point to it within minutes. It takes time for the virtual directory to resolve itself. This is the one element that I was missing and I was very upset, but the next morning it worked fine. Imagine that.
  2. The paths of the images and links will point towards the other old website folder. Go through and change them, before you start adding more. All the images should be in your new directory folder, but the old folder name will be in the path of the html code. All this is stored in the database, so if you switch back, you will have to change them back. This may support a case of keeping the images in a separate folder than the portal. I don’t know if that is possible real fast.

 

 

Comments are closed.