3 results found
-
Allow copying the original value for Non-CultureSpecific fields inside Culture Specific list properties during auto-translate operation
For some blocks we use list properties and define them as Culture Specific. And if there is a non-culture specific field inside the list item block type, the value is not copied or translated due to the implementation in EpiServer code.
For this case we need to find a way to copy the original value from the master language branch while translating the content. Please add a feature to customize this behavior.
Thanks.
1 vote -
Support keeping the original values for technical fields during auto-translate
We have a culture specific string field in one block type which is decorated by custom "AutoSuggestSelection" attribute. The attribute allows us to select predefined list of icon types. The problem we face is that the field is a technical field which should not be translated. Even possible it should be copied from the master language. But translation provider automatically translates the field value if it is string and culture specific.
Please add an option for skipping/copying technical fields during auto-translate operation
1 vote -
When duplicating content for new language need to add draft content along with published content
We need capability when we are creating content for a new language version for a page, from master language draft content also along with published content should be available, Currently only either published language version or draft version can be added but not both.
We are using EPiServer.Labs.LanguageManager add on to create new language content.
Can this add on EPiServer.Labs.LanguageManager be extended to provide this option.
1 vote
- Don't see your idea?