You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When content is converted from a content that has a single language to multiple via 'Allow varying by culture' then some of the property values my not be synced correctly.
background
when you have content in a single language and then convert it to support multiple languages, Umbraco goes from storing the content with no culture to storing it with a culture. Unfortunately when it does this it doesn't remove the existing content stored with no culture.
uSync exports all values for a property. which means during the sync. you will see all the values. including the now obsolete values stored without culture.
during an import, uSync attempts to work out which is the best way to import this data. however if it encounters a value without a culture next to values with cultures it considers the value to be broken and moves on to the next property.
what it should do is just consider that 'value' to be broken and move on to the next value.
When content is converted from a content that has a single language to multiple via 'Allow varying by culture' then some of the property values my not be synced correctly.
background
when you have content in a single language and then convert it to support multiple languages, Umbraco goes from storing the content with no culture to storing it with a culture. Unfortunately when it does this it doesn't remove the existing content stored with no culture.
uSync exports all values for a property. which means during the sync. you will see all the values. including the now obsolete values stored without culture.
Issue
during an import, uSync attempts to work out which is the best way to import this data. however if it encounters a value without a culture next to values with cultures it considers the value to be broken and moves on to the next property.
what it should do is just consider that 'value' to be broken and move on to the next value.
7653143 fixes this!
The text was updated successfully, but these errors were encountered: