Juraj,
I have updated my code to reflect yours and by changing
var ENpage = tree.SelectNodes(Constants.Kentico.PageType.SharePointVenueItem)
.Path(kenticoTopContainerPath, PathTypeEnum.Children)
.WhereEquals(SharePointGenericColumns.ID, spVenueObj.ID)
.Culture("en-US")
.OnCurrentSite()
.TopN(1)
.FirstOrDefault();
By
var ENpage = DocumentHelper.GetDocuments()
.Types(Constants.Kentico.PageType.SharePointVenueItem)
.Path(kenticoTopContainerPath, PathTypeEnum.Children)
.WhereEquals(SharePointGenericColumns.ID, spVenueObj.ID)
.Culture("en-US")
.OnCurrentSite()
.TopN(1)
.FirstOrDefault();
Staging tasks are now created.
In your code example, could you confirm that if you select an existing page by TreeProvider.SelectNodes()
and update it, you won't have a staging task?
If yes, does it mean that DocumentHelper.GetDocuments()
is the only method for generating staging logs/tasks?
What is the difference between the SelectNodes and GetDocument methods?
Is GetDocuments slower than the SelectNodes? I have thousand of pages to be created on the fly and I want to make sure that I am using the most efficient code for creating/updating them.
Thank you,
Sylvain