Hello Lee and friends,
This question is regarding an older revision (not version) of dotnetnuke. A situation occured in which a table somehow was deleted fromt he database and I wanted to see what a particular dotnetnuke page said without a critical error message do to this missing table. Having had some prior database backups I decided to backup my current development database and than restore the old one (from a month ago) back on to the sql 2005 express database.
Suffice it to say I didn't have the files from that time period but did have the dotnetnuke files from the ftp server as of about 7 days ago before I had done a major upgrade to my development database which was a storefront. So I decided I would go ahead delete the current database and restore this older database with the newer dnn files I had backed up fromt he server a week prior.
Was I in for a surprise to say the least I edited the web.config file to reflect the local database and connection ad I always would do when on a development environment however this time instead of going to the localhost I was redirected to the live server in which this framework was installed on.
I must also say I went ahead and created a new folder in myc omputer and a virtual folder to match it called dotnettest and put all needed permissions such as aspnet authentication on the folders and pointed iis to it and all the rest. However no matter how many times I attempted to load the
http://localhost/dotnettest I was redirected the the production site of the server.
I than discovered what was causing this to happen in the web.config file and noticed a couple lines in it under the httpModules tag a child of httpHandlers. So I commented out the following two requred to not get this redirect problem the lines were as follows:
------------------------------------------------------------------------------------------------------------------------------------------------------------------
< add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" >
< add name="UrlRewrite" type="DotNetNuke.HttpModules.URLRewriteModule, DotNetNuke.HttpModules.UrlRewrite" >
---------------------------------------------------------------------------------------------------------------------------------------------------------------
When those two lines were commented out it appeared as if the rest of the web.config file was being read however I got a simple dotnetnuke message that an error had occured with no other instructions.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Having said all this is their anyway to restore an older revision of a database while using newer dotnetnuke files from the ftp server when their hasn't been a major upgrade like another web application or perhaps new module written to it. The only thing I can think of is that the older version did contain this one extra table in the database and the newer one did not. Do any of the files stored on the ftp server (not database) point to all tables in the database so if one were missing in the database the web.config file loading everything up would freak out.
I am just trying to understand why it is that when I backed up files and database from the same exact time period I never got redirected by the httpredirect module to the live production site but when I use a older revision of the database with a new set of dnn files fromt he ftp server I either get redirected to the production site or if I comment out the lines responsible for this I get an error that their is no information about.
Lastly where can this URLrewrite module be found and how would it know to redirect me to the production site if a problem existed in the development arena thanks so much for your help in this regard
Bo