8 results found
-
Language Manager Role wise access
In the Languages gadget (Language Manager add-on), users have the option to duplicate content when creating a new language branch. During this process, the “Duplicate content” dialog presents checkboxes for:
Add all children
Add related content(s)
These options are useful for administrators but pose a risk when used by editors who may not fully understand the implications. For example, an editor in our organization mistakenly duplicated a section with over 800 nodes, resulting in around 500 duplicated blocks. This caused significant manual cleanup and unnecessary content clutter.
Feature Request:
We would like the ability to restrict visibility or access to…
2 votes -
Language Manager in combination with the auto translate feature
Language Manager in combination with the auto translate feature
2 votes -
1 vote
-
[Language Manager] Improve the warning message to make it more meaningful
When translating the pages, you might get the following error:
"Error occurs while translating content, please check the logs for more details."Reason:
In most of cases, the issue happens when the page contains a block that was not enabled for the target language.
For an example: when translating a page from EN -> SV. The page contains a block in ContenArea. The issue happens when the 'sv' language is not enabled for the block.Solution:
As the above example, please enable 'Sv' language for the block.I think we need add more information to the message to make it…
1 vote -
Language Manager won't let you exclude terms, translates Block Names
As a Content Manager, I want to be able to translate pages with an exclusion list which prevents specific words and terms (e.g. Brand Names, Product Names) in content, and Block/Image/Object Names (i.e. Internal Objects which need to be in my native language to administer) from being translated.
Currently, the add-on translates key terms and names and the content manager needs to identify these and translate them back again, but these changes are subsequently lost if the content is re-translated. By managing these globally through a dictionary (or a setting, for Block Names, etc), this would massively improve the admin…1 vote -
Hreflang Tags
Auto-include hreflang tags in the existing CMS page.
For example, when translating a page from English to French, the system (the Languages gadget) auto-generates an hreflang between the two pages. That is, the English page has an hreflang to the French page and vice versa. We would also like the system to auto-generate self-referencing hreflangs for each page (i.e., English page to itself and French page to itself).
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 -
Auto-translate
I use Auto-Transalte a lot but I don't want the Name, URL and Reference to be translated automatically.
When handling multiple language websites it is practical to keep the Name, URL & Reference in English.
The URL I can change manually if necessary
1 voteThank you for raising this feedback request. We will continue to gather feedback to assess demand for this functionality.
- Don't see your idea?