uSync: Imported translations get flat structure instead of being nested

Questions
1

Hi

We have an Umbraco 13.7.1 with uSync 13.2.6. When we import translations into a clean Umbraco database, they don’t get placed in the original structure, but rather in a flat list.

In this image you can see the imported translations (for every period there was supposed to be a new level in the structure as in the “source” Umbraco environment):

image
image1947×981 51.1 KB

We recently upgraded Umbraco from 13.6 to 13.7.1. In 13.6 the translation import worked fine for a clean database.

The uSync files seem to be correct in regards to the parent node, e.g.

<?xml version="1.0" encoding="utf-8"?>
<Dictionary Key="68e7809c-57c9-495f-9f9f-d16a0f830dea" Alias="Cart.Errors" Level="1">
  <Info>
    <Parent>Cart</Parent>
  </Info>
  <Translations />
</Dictionary>

We’ve tried making a Clean export from the Umbraco which has the correct Translations structure and overwrite the uSync files locally, but only the whitespace seems to be a bit different - and the import on the clean database still gives us the flat structure.

Can we do anything to make the import work/give us the correct structure?

2

Hi,

I will take a look at this - but just quick test on the latest versions and running the import for a second time should put the items into the tree.

3

there is indeed something strange in the update of Umbraco from v13.6 t ov13.7. that causes this.

I think its this change ( Cache null dictionary values by key by callumbwhyte · Pull Request #15576 · umbraco/Umbraco-CMS · GitHub ) but someone who understands the caching of the repositories would have to understand why :wink:

It appears to cause the lookup for the parent to fail when the parent has just been added previously (so it’s caching somewhere)

We can work around it (change here) - so we we will update things to do that, but also might put something against this change incase anyone can spot and fix it in the core,.

4

Thanks for looking into (and fixing) it so quickly. :raising_hands:

We will await the next version of uSync. :+1:

5

Workaround/Fix for this is in now in the uSync v13.2.7 release

6

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.