Planning Ahead for Evotiva DNNBackup
This is an optional modification. If you are not using Evotiva DNNBackup in the way that I am, you can ignore this section.
I wanted to be able to create portals locally and upload them (clone them) with Evotiva DNNBackup to a production server. I especially wanted to be able to install and test modules locally without risk of shutting down an entire production site. The first time I did this, I created a local portal named vnwweb_712 that was accessed as localhost/vnwweb_712. When I uploaded to the production site, vnwweb.com, the internal URLs on the site that called internal pages were hardcoded as /vnwweb_712/pagexxxx and gave 404 File Not Found errors. Presumably if I'd had the local web site named localhost/vnwweb, that would not have been a problem.
The solution to this issue was to re-create the site on my local machine with the name vnwweb_712.local which resulted in the URLs for the internal pages on the production server becoming /pagexxxx.
There were several changes needed to do this, including creating a new website reconfigured differently in IIS (covered on another page).
The first change was to create a new record in the hosts table in the hosts file as '127.0.0.1 vnwweb_712.local'
127.0.0.1 is the 'universal' local host IP number.
Host table is in a file named 'hosts' located at C:\Windows\System32\drivers\etc\ . If you browse to that folder, you will see a file named 'hosts'.
1. Navigate to the folder. Double click on the hosts file, then select Notepad as the editor of choice.
2. Add the line to the hosts file. This image shows the addition of the entry '127.0.0.1 vnwweb_712.local' (without quotation marks). Replace the vnwweb_712 with whatever the name of your website will be (or is).
Note: When I tried to save the modified file, I got a message saying that I didn't have permission to make changes in the file in that location but that I could save it somewhere else. I am the admin of the computer, so I'm not sure why I got the error.
3. The solution was to right-click on the hosts file, then click on Properties.
4. Click on the Security tab, click on Edit.
5. Enter the user name then click on Check Names to see if user exists. If exists, will appear underlined in box. Click OK.
6. Check boxes to assign 'modify' permissions to that user. Click OK and Click OK.
This allowed permission for my username to save the modified hosts file.
You may need to reboot for this change to take effect.
Following IIS configuration (covered on on another page), this change will allow you to browse to your local portal using the URL vnwweb_712.local when this URL is entered in the Bindings dialog box in IIS for this website.