After running into the issue more than once of needing to edit the web.config or a remote DotNetNuke installation, I decided to build a simple module to do just that. Most recently I have came into this issue with upgrading a site to use .Net 3.5 without have FTP access to the site. I used LinqPrep to do most of the heavy lifting and then used the ConfigEditor to tidy up a few spots. The combination of these two modules made the process quick and painless. I understand that the 5.x release of DotNetNuke has an option to upgrade the installation to 3.5 using a Host Setting. However, I am sure there are many of us that will be managing sites on a 4.x release for sometime into the future.
If this happens to describe your circumstances or you would like to change some of the provider settings in the default configuration, add or edit appSettings or connectionStrings or anything else in the web.config file. this module may come in very handy! Also if you would like to be able to use the really cool features provided by new versions of .Net, the combination of LinqPrep and ConfigEditor will make it very easy to change the configuration to reference versions of .Net released after 2.0.
The OpenLight ConfigEditor is a streamline module that simply pulls the content of the root web.config into a text box and lets you make changes to it. I thought it would be helpful to also allow for a backup to be made of the current file. So, there is a checkbox to enable a copy to be made and a textbox used to specify a file name to copy the current web.config file to. This file is saved into the current portal’s home directory with a .ceb (ConfigEditor Backup) file extension automatically appended to it.
ConfigEditor also allows you to select a file and restore the contents of the file back to the root web.config. The restore process allows you to select files with a .ceb extension. This will hopefully prevent accidently restoring some random text file to the web.config… that, of course, would be very bad!
Please keep in mind if the web.config becomes invalid, you will more than likely not be able to access the module’s restore function. This option is available to rollback from a valid configuration to a previous configuration. If the modifications made to the web.config file are in fact invalid you will have to restore the file using FTP, RDP or some other method available from your hosting provider. Due to these reasons, the initial release of this module only allows SuperUser accounts to access the edit and restore functionality.
We hope this module is useful to many of you and please remember we are always eager to hear your feedback and suggestions.