I am running an Umbraco 8.17.1 application with uSync + Content Edition 8.10.5 and DocTypeGridEditor 1.2.7. The application is deployed to multiple azure app services environments (test, production). Previously, everything worked great with deploying and using uSync to update all the content, including the DocType Grid Editors.
I recently adjusted the DocTypes used in the grid editor to include Nested Content. Now when I deploy, it looks like the IDs in the Nested Content are being changed for each environment which causes them to not sync properly. After publishing new content, only the top-level properties of each page are synced correctly. All the Nested Content components do not get updated and appear empty.
I saw this similar thread which seems like the same issue, but with my setup, it is not working. Is there something additional I need to configure to get this to work smoothly?
the encoding of the json in doctypegrid editors inside the grid, is a little diffrent to how the json is encoded inside the same properties outside of the grid, and it means this happens (ths issue was with repeatable strings but i think its the same for you).
release wise, we are just working through these release now, it might not be today but first thing next week there should be a fix.
I think I have a related issue. Somehow, we have Nested Content in DTGE that appears empty in the backoffice, but renders fine on the website. Comparing the grid JSON of the problematic content with others using the same DTGE but working properly in the backoffice, I see the following:
Left: no issues; Right: appears empty in the backoffice
I am not sure how this happened, maybe we imported content using the older uSync version that had the bug. With the latest version, we don't get any issues.
The problem now is we have a production website with many instances of this issue. Is there any way to fix this without having to manually recreate the content?
uSync, DocTypeGridEditor, Nested Content Publishing Issue
Hello,
I am running an Umbraco 8.17.1 application with uSync + Content Edition 8.10.5 and DocTypeGridEditor 1.2.7. The application is deployed to multiple azure app services environments (test, production). Previously, everything worked great with deploying and using uSync to update all the content, including the DocType Grid Editors.
I recently adjusted the DocTypes used in the grid editor to include Nested Content. Now when I deploy, it looks like the IDs in the Nested Content are being changed for each environment which causes them to not sync properly. After publishing new content, only the top-level properties of each page are synced correctly. All the Nested Content components do not get updated and appear empty.
I saw this similar thread which seems like the same issue, but with my setup, it is not working. Is there something additional I need to configure to get this to work smoothly?
Thanks!
Emily
Hi Emily,
i think this is something we have recently (as in today) fixed for v9 and we have ready to put into v8.
https://github.com/KevinJump/uSync/issues/323
the encoding of the json in doctypegrid editors inside the grid, is a little diffrent to how the json is encoded inside the same properties outside of the grid, and it means this happens (ths issue was with repeatable strings but i think its the same for you).
release wise, we are just working through these release now, it might not be today but first thing next week there should be a fix.
Perfect. I will watch for that release next week and update this if it is fixed. Thanks for your quick reply!
Update: Upgrading to uSync 8.10.7 fixed the issue. Thanks again!!
Hi Kevin,
I think I have a related issue. Somehow, we have Nested Content in DTGE that appears empty in the backoffice, but renders fine on the website. Comparing the grid JSON of the problematic content with others using the same DTGE but working properly in the backoffice, I see the following:
Left: no issues; Right: appears empty in the backoffice
I am not sure how this happened, maybe we imported content using the older uSync version that had the bug. With the latest version, we don't get any issues.
The problem now is we have a production website with many instances of this issue. Is there any way to fix this without having to manually recreate the content?
is working on a reply...