Dealing with very large websites in Umbraco regarding republishing due to errors
Hi,
I am in the process of building a new website in Umbraco (well it is more of a case of migrating an old website to umbraco). I am running Umbraco 4.7.1.1. The website has over 40000 pages and it will continue to grow, I have separated the pages out into year, week and then category folders to ensure that I do not have a very large number of nodes under one node. This all seems to be performing fine in the backend but my concern is what happens if I ever get an issue that requires me to republish all the nodes?
I have had situations in the past where umbraco has had issues with a node and it has meant that all nodes lose their link to document and it is replaced with a '#'. I did in fact have a similar issue earlier today when testing on this site, I deleted a document type that one of my pages was using and it meant every single node in the website lost its link to document.
Usually if these situations arise then the answer is often to republish all the nodes by right clicking on the top level node and selecting "Publish". As you can imagine with over 40000 nodes this is going to keep timing out and it will also take a very long time to complete, the site could be offline for days in this scenario.
I just wondered what options I have if the site was every to have such issues when live? Is there an easier or quicker way to republish all of the nodes, or a way to find out what node within the site might be causing an issue and taking the rest of the site offline so that just that node can be republished or removed?
Dealing with very large websites in Umbraco regarding republishing due to errors
Hi,
I am in the process of building a new website in Umbraco (well it is more of a case of migrating an old website to umbraco). I am running Umbraco 4.7.1.1. The website has over 40000 pages and it will continue to grow, I have separated the pages out into year, week and then category folders to ensure that I do not have a very large number of nodes under one node. This all seems to be performing fine in the backend but my concern is what happens if I ever get an issue that requires me to republish all the nodes?
I have had situations in the past where umbraco has had issues with a node and it has meant that all nodes lose their link to document and it is replaced with a '#'. I did in fact have a similar issue earlier today when testing on this site, I deleted a document type that one of my pages was using and it meant every single node in the website lost its link to document.
Usually if these situations arise then the answer is often to republish all the nodes by right clicking on the top level node and selecting "Publish". As you can imagine with over 40000 nodes this is going to keep timing out and it will also take a very long time to complete, the site could be offline for days in this scenario.
I just wondered what options I have if the site was every to have such issues when live? Is there an easier or quicker way to republish all of the nodes, or a way to find out what node within the site might be causing an issue and taking the rest of the site offline so that just that node can be republished or removed?
Any input or suggestions are welcome.
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.