I have setup installed Umbraco V8.4.1 and licensed uSync Complete (v8.5.0) for my client and deployed on Azure App Services. (develop, uat, prod). Everything is setup and seemed to be working well. However on publishing either through direct server to server publish or via serialisation to disk export/import. Content is being lost on the target server.
We are using
DocTypeGridEditor (v1.1.0) and Nested Content which apparently uSync works with. We have created modules with related partial views, then each module has content which could be Nested Content Lists, Multi Url pickers, colour pickers or basic Richtext, Textbox values. However after publishing a page containing the GridView with DGTE only the first level basic properties of each Module are successfully transferred (Richtext, Textbox etc). All more complex components like 'Nested Content' Lists, MultiUrl Lists etc their content is not transferred and they appear empty. Interestingly the page content as a whole is transferred so the content gets published but you can't edit it on the target server as it doesn't exist as content nodes.
I've been looking into Content Mappers but you docs say DGTE and Nested are already compatible, perhaps I need to configure it more? Or perhaps its not looking deep enough into the content? Can you advise on how I can go about debugging and fixing this issue?
On the target site do the doctypes that are being used as the nested doctypes exist (it might be a dependency error, not working out that it needs to create those doctypes)
Yeah this is an issue in uSync.ContentEdition :( - its not storing the JSON of the nested values inside the JSON of the DocTypeGrid Editior correctly 😥
uSync Complete DocTypeGridEditor, Nested Content Publishing Issue
Hi,
I have setup installed Umbraco V8.4.1 and licensed uSync Complete (v8.5.0) for my client and deployed on Azure App Services. (develop, uat, prod). Everything is setup and seemed to be working well. However on publishing either through direct server to server publish or via serialisation to disk export/import. Content is being lost on the target server.
We are using DocTypeGridEditor (v1.1.0) and Nested Content which apparently uSync works with. We have created modules with related partial views, then each module has content which could be Nested Content Lists, Multi Url pickers, colour pickers or basic Richtext, Textbox values. However after publishing a page containing the GridView with DGTE only the first level basic properties of each Module are successfully transferred (Richtext, Textbox etc). All more complex components like 'Nested Content' Lists, MultiUrl Lists etc their content is not transferred and they appear empty. Interestingly the page content as a whole is transferred so the content gets published but you can't edit it on the target server as it doesn't exist as content nodes.
I've been looking into Content Mappers but you docs say DGTE and Nested are already compatible, perhaps I need to configure it more? Or perhaps its not looking deep enough into the content? Can you advise on how I can go about debugging and fixing this issue?
Many thanks in advance.
Mike
Hi Mike,
can you share your doctype grid config ?
As you say (or I say!) it should work
Also just to check :
On the target site do the doctypes that are being used as the nested doctypes exist (it might be a dependency error, not working out that it needs to create those doctypes)
Hi Kevin,
Thanks for the quick response! Yes this is the config:
The target server in UAT is identical to the source server. Other information: File sync is flat and by ID
Other packages installed: Also using SeoChecker, ModelsBuilder API, AzureBlobProvider for media.
Hi,
Yeah this is an issue in uSync.ContentEdition :( - its not storing the JSON of the nested values inside the JSON of the DocTypeGrid Editior correctly 😥
but - we've fixed it 🥳- https://github.com/KevinJump/uSync8/issues/83
And pushed out a patch fix for content edition. 🎉 https://www.nuget.org/packages/uSync.ContentEdition/8.5.0.1
So updating content edition on each site will fix this.
Amazing thanks Kevin, will give it a try now..... will post the result shortly..
.....
Just tested and everything working nicely now! Thanks so much for the support!
Cheers
Mike
is working on a reply...