Streamline usage of l10n_mode
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.
#2 Updated by Andreas Allacher about 3 years ago
So with this change there will be no way to refresh mergeIfNotBlank values once the record was localized?
Which might be interesting for relation fields. Of course, with Inline records there is the synchronize / localize all functionality but it has to be executed in each language manually.
A nice possibility would be to implement it similar to the exclude mode with this changes. However, then one would have to keep track regarding changes in the child record - we don't want to remove those chnages (as it would be like a non empty field).
Probably way too complex though. With the changes regarding exclude mode, most possibilities should be handled (there is always the copy option)