I am working with a client who attempted to setup a bulk publish where a 'section' node (which contains many descendant nodes of various types) by using the Publish At... feature. They find later however that instead of publishing correctly, all the content (i.e. body text, etc) is lost and the following error message can be found on the audit trail for the affected nodes:
Error publishing node: System.ArgumentException: No Document exists
with Version '{GUID}'
I noticed that there have been various instances of this error caused by orphaned versions reported so we tried cleaning up orphaned versions on the database but that did not bring back the content.
This is for a site with a fairly large amount of content running on Umbraco 4.11.8.
Any ideas? Would it have helped if instead of publishing everything at the same time, the publishing was staggered over a period of time?
Missing content after a bulk publish
Hello
I am working with a client who attempted to setup a bulk publish where a 'section' node (which contains many descendant nodes of various types) by using the Publish At... feature. They find later however that instead of publishing correctly, all the content (i.e. body text, etc) is lost and the following error message can be found on the audit trail for the affected nodes:
I noticed that there have been various instances of this error caused by orphaned versions reported so we tried cleaning up orphaned versions on the database but that did not bring back the content.
This is for a site with a fairly large amount of content running on Umbraco 4.11.8.
Any ideas? Would it have helped if instead of publishing everything at the same time, the publishing was staggered over a period of time?
is working on a reply...