I am trying to set up a local development copy of a live Umbraco site. I copied the wwwroot down to my local machine. I change the web.config to point to the development SQL server. If I navigate to localhost/umbraco/ I see my content nodes and content, although rather slowly. If I navigate to localhost, I get a message about no pages being found and a screen trying to guide me to set up Umbraco for the first time.
I did a republish on the entire site and now it seems to be working. Is this a cache issue? Is there something that needs to be flushed/rebuilt when copying/moving the site?
I did a couple of deployments like that today. Copying the DB to a new server, and copying the files to a new IIS. I also had to do the "Republish entire site" trick to get it to pick up on the actual content.
yes you would have to do this to update the local cache files, otherwise they are probably all pointing to the live version URL. It just needs a kick to rebuild the site.
We have the same issue when we work locally, then check in. We need to log onto the staging version and republish to update the cache on our dev servers.
Installing local copy - no pages found
I am trying to set up a local development copy of a live Umbraco site. I copied the wwwroot down to my local machine. I change the web.config to point to the development SQL server. If I navigate to localhost/umbraco/ I see my content nodes and content, although rather slowly. If I navigate to localhost, I get a message about no pages being found and a screen trying to guide me to set up Umbraco for the first time.
Any ideas?
I did a republish on the entire site and now it seems to be working. Is this a cache issue? Is there something that needs to be flushed/rebuilt when copying/moving the site?
I did a couple of deployments like that today. Copying the DB to a new server, and copying the files to a new IIS. I also had to do the "Republish entire site" trick to get it to pick up on the actual content.
So I guess it is by design.
yes you would have to do this to update the local cache files, otherwise they are probably all pointing to the live version URL. It just needs a kick to rebuild the site.
We have the same issue when we work locally, then check in. We need to log onto the staging version and republish to update the cache on our dev servers.
is working on a reply...