Umbraco 16: When copying blocks to different languages, the properties come up empty

Questions
1

When I copy a block to different languages ​​in Umbraco 16, its properties (textstring, image) are empty. What is the reason for this?

2

Hi @alperenkapusuz58

Can I ask you to share your Document-Type configurations?

From my assumption, the configuration would be in this way:
Variant Document with an Invariant Property with a Block based on a Variant Element-Type with Varying Properties.

Does that sound like your case?

Thanks in advance

3

Of course I share

  • Document Type: ProductPage
  • Culture Variant: Yes
  • Properties:
  • PageTitle → Variant (different per culture)
  • SeoDescription → Variant (different per culture)

It is like this

4

Thanks, @alperenkapusuz58

I need a little more of the picture.
Like, where are the Blocks on ProductPage and how are they configured :slight_smile:

Thanks

5

Hi Niels,
Having this issue as well.

Steps:

  1. Create a element type - vary by culture with two different fields, one text field that is not shared across cultures. One image field that is shared across cultures

  2. Create a block list with this element type

  3. Add the block list to your content type

  4. Try to copy between one language and another

    Result: the image is copied (or inherited) but the text field is blank.

Is this correct behavior? I’d rather have the texts copied as well.

Umbraco 16.2

6

Hi @Herman

Thank you for sharing your experience. I’m starting to see a pattern now, based on a few other conversations. — I’m still not sure how the CMS Configuration experience can be changed to accomondate the interpretation, but if you have ideas please let me know.

If your Element Type is set up to Vary by Culture, then you can say that it’s been configured to exist in Culture Shared data — That the Block is a container for data of multiple cultures.
This means the data of the Block then becomes Culture specific, and when you then copy that over to another culture, the data of the block is still declared as the Culture is was created in.

In other words, setting your Element Types to Vary By Culture, only makes sense if used in a Block Editor on a Property that is Shared Across Cultures.

I hope this helps, let me know what you think :slight_smile: