Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Categories Editing
Created by Guest
Created on Oct 11, 2023

Language Manager errors translating for Blocks with Block List properties

I have a block which uses IList<Block> style properties for managing collections of data against the parent block rather than forcing the Content Editor to have to navigate between parent and children in the editor interface.

My solution has Inline Blocks turned on and is using the Optimizely Labs Language Manager Add-On

When the block is a shared block and I try and translate the block I get an error from the Language Manager and the new translation is empty with just the first instance of an empty child block created. In the logs I see this error message:

EPiServer.Labs.LanguageManager.Business.LanguageBranchManager: Error: Error when saving the content 205_820: Invalid use of read-only object, call CreateWritableClone() to create a writable clone.

When the block is an inline block and I try and translate the page, the page and the inline version of the same block are successfully cloned into the new language.

Expected Result

A block with IList<Block> properties should successfully be cloned in the following scenarios:

  • When translating the Shared block into a new language via Language Manager: Fails

  • When translating the inline block as part of translating a page into a new language via Language Manager: Passes

  • Guest
    Oct 17, 2023

    This is fixed in EPiServer.Labs.LanguageManager version 5.2.0