Transfer files to host space. Relax security on all sub-folders, letting the NETWORK SERVICE or similar create and modify files. If installing over existing files, you still need to reset the security on the folders, cascading the settings to children files. I usually double check permissions after any install or upgrade, because a security fail can cause all sorts of seemingly unrelated troubles.
If upgrading between builds, these folders are the ones to replace:
- bin
- config (Backup and restore any custom changes, e.g. umbracoSettings.config)
- umbraco
- umbraco_client
Use the modified detect.ascx in the install/steps folder, which plays nice with dailyrazor. The modified detect.ascx has set the visibility of "Upgrade" and "Install" buttons in lines 85 and 86 to true, letting user proceed even if umbraco can't write to web.config.
Editing the web.config file:
- Setting the ConfigStatus to empty causes umbraco to go through install steps
- After umbraco finishes installation, set ConfigStatus to 4.0.0
- Set database connection string (Limited Permissions prevent umbraco from doing this automatically on dailyrazor)
- SMTP Information should be set
- Generally, you'll end up wanting C# Debugging set to true
- Also set CustomErrors to Off, from RemoteOnly (Return these last two to defaults once site is running smoothly)
In the config folder:
- In umbracoSettings.config Set default mail info
- Also in umbracoSettings set true for prefixes to enable subdomains
Only go through installation steps for version upgrades if database changes are required. Upgrade the database in this case, not install anew.
At some point, Right-Click on the Root Page in the Content Tree, and select Manage Hostnames. Add first preferred hostname, like "feebdack.com", then less preferable hostname, "www.feebdack.com". Subdomains will be added here also.
