#101564User Interface related translation issues
Description
This is a sub container to collect issues that are related to the user interface during translation processes
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[TASK] User Interface related translation issues Resolves: #101564 Releases: main
Related issues 17
- Bug #76274Translate Button does not work when no Access to Default language
- Feature #78610Allow record localization from non default language in the list module
- Bug #88965Siteconfigurations fallbackType "strict" shows free contents
- Bug #88966Backend translation of contents should show warnings related to defined fallbackType from Site Configuration
- Feature #89162Provide possibility to switch from connected mode to free translation mode (and vice versa)
- Bug #89448Translation Wizard can get stuck
- Bug #89520Missing tooltips in info module
- Bug #90051User get stuck when translation wizard fails
- Bug #92909Page Translation list is not orderable, but is rendered always in first position
- Bug #92987Preview of page from docheader button shows root page when starttime is set
- Bug #96413Translated content is not shown in backend when deflangBinding = 1 and freemode is used
- Bug #97094Transl.Orig field for content element creates confusing translation status
- Bug #97763Translation Button shown eventhough already translated
- Bug #98172Translate button still appearing despite all content elements being connected, page being in Connected Mode
- Bug #101415Cannot localize page in backend
- Bug #101876Localization overview: button to create localizations not clickable
- Bug #102345Copy/Move pages with existing translation into another site with different language setup results in orphaned problematic page translation records