Issue Task Closed

#79241Streamline usage of l10n_mode

Oliver Hader 01/10/17, 12:06 updated 04/12/25, 17:51

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