Task #79244
openTask #79241: Streamline usage of l10n_mode
Streamline l10n_mode exclude data processing
0%
Description
Basically localizations can happen in two different modes - either the connected mode (localization belongs to a parent language record) or the free mode (localization has a language, but does not depend on any parent).
For fields having l10n_mode set to exclude in the connected mode, the values of the parent language record shall be cloned to all particular and dependent localization records each time the parent record gets updated (or created).
On the other side l10n_mode exclude does not make much sense in the free mode, since there's no concept of any parent in that regard. In this scenario the value is cloned from the parent language record once during the creation of the localization record. In the context of the localization, the field value is shown and can be modified without any restrictions.
Updated by Philipp Gampe over 7 years ago
- Related to Bug #81761: l10n_mode exclude is ignored in IRRE relations and deletes unrelated child records during l10n added
Updated by Susanne Moog over 5 years ago
- Status changed from New to Needs Feedback
- Assignee set to Oliver Hader
Is this task still up-to-date? Afaics the value of l10n exclude fields is already copied when translating.
Updated by Oliver Hader over 4 years ago
- Related to Bug #80141: Add allowLanguageSynchronization chain resolving added
Updated by Oliver Hader over 4 years ago
- Status changed from Needs Feedback to Accepted
Seems like this has been addressed in #80141 already (after this very issue has been created).
l10n_mode=exclude
for free mode: Record 298
is copied to language 1
as record 303
¶
l10n_mode=exclude
for connected mode: Missing test case¶
→ there should be a new test case localizeContentWithLocalizationExclude