Recreate umbraco.config or another way to republish all content
I'm facing problems updating a large site with around 9000 sites where I programmatically have unpublished a lot of nodes. Using the UnPublishSingleNode crashes the server, so I'm looking for other options where the umbraco.config file is recreated based on latest changes being done.
I tried renaming the file to see if it would be recreated, but it did not do the trick for some reason... Anyone know how to do?
Have you tried republishing entire site, by right clicking on the content node (top-level) and choose that option, or recycle the application pool? I imagine unpublishing 9000 sites/pages may have timed-out in the process. You may want before running a large procedure like to increase your timeouts.
The timeout is already set to 3600 seconds, so should be enough. What seems to happen (according to the ISP) is that the cpu goes through the roof and the application pool is recycled automatically when I try republishing too many nodes at the time.
So basically I was thinking that there should be a way to recreate the umbraco.config file where the file is created in one instance instead of multiple instances. Republisihing the entire site sounds like the correct tool for this, but for some reason it won't do the magic...
Recreate umbraco.config or another way to republish all content
I'm facing problems updating a large site with around 9000 sites where I programmatically have unpublished a lot of nodes. Using the UnPublishSingleNode crashes the server, so I'm looking for other options where the umbraco.config file is recreated based on latest changes being done.
I tried renaming the file to see if it would be recreated, but it did not do the trick for some reason... Anyone know how to do?
Have you tried republishing entire site, by right clicking on the content node (top-level) and choose that option, or recycle the application pool? I imagine unpublishing 9000 sites/pages may have timed-out in the process. You may want before running a large procedure like to increase your timeouts.
http://msdn.microsoft.com/en-us/library/e1f13641(VS.71).aspx
-Chris
Sorry, link didn't format. Wonderful microsoft urls.
http://msdn.microsoft.com/en-us/library/e1f13641(VS.71).aspx
The timeout is already set to 3600 seconds, so should be enough. What seems to happen (according to the ISP) is that the cpu goes through the roof and the application pool is recycled automatically when I try republishing too many nodes at the time.
So basically I was thinking that there should be a way to recreate the umbraco.config file where the file is created in one instance instead of multiple instances. Republisihing the entire site sounds like the correct tool for this, but for some reason it won't do the magic...
Don't know why or how, but suddenly all unpublished items were gone. Problem solved... ;)
Glad to hear it finally worked :).
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.