#79241Streamline usage of l10n_mode
Description
The TCA configuration property l10n_mode currently allows to define several behaviors concerning localization per individual column. In the long run it shall be possible to select localized records directly without having the requirement to fetch the parent default language record first to overlay particular field values.
This is the plan for the current existing variants for l10n_mode:- exclude: will stay, but value from parent language record will be cloned to localization
- mergeIfNotBlank: will be removed, value from parent language record will be cloned to localization (if empty/blank) & removes the feature of merging values during runtime
- noCopy: will be removed
- prefixLangTitle: will stay, still adding the prefix to the cloned localization
- default: will stay, still cloning value from parent language record to cloned localization
This umbrella issue collects issues for TYPO3 CMS 8 only. Fixing the behavior in existing LTS versions is a different topic.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Subtasks 10
- Feature #35273l10n_mode option mergeIfNotBlank should handle empty ids correctly
- Bug #59192mergeIfNotBlank with FAL records
- Bug #65863content_fallback / mergeIfNotblank fails with content slide, pageOverlayFields is ignored
- Bug #66206l10n_mode mergeIfNotBlank does not work for in specific Mapping configuration (inline / direct mapping - no ObjectStorage)
- Feature #78169Add field for the record translation mode (connected vs free)
- Task #78745Get rid of localizationMode of TCA type inline
- Feature #78959Non-translated sys_file_reference with "mergeIfNotBlank" doesn't work
- Task #79242Remove l10n_mode noCopy
- Task #79243Remove l10n_mode mergeIfNotBlank
- Feature #79658Introduce allowLanguageSynchronization