Project

General

Profile

Actions

Task #79241

closed

Streamline usage of l10n_mode

Added by Oliver Hader about 7 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2012-03-27
Due date:
% Done:

91%

Estimated time:
(Total: 0.00 h)
TYPO3 Version:
8
PHP Version:
7.1
Tags:
Complexity:
Sprint Focus:

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.


Subtasks 11 (1 open10 closed)

Task #79242: Remove l10n_mode noCopyClosed2017-01-10

Actions
Task #79243: Remove l10n_mode mergeIfNotBlankClosed2017-01-10

Actions
Task #79244: Streamline l10n_mode exclude data processingAcceptedOliver Hader

Actions
Feature #78959: Non-translated sys_file_reference with "mergeIfNotBlank" doesn't workClosed2016-12-12

Actions
Bug #65863: content_fallback / mergeIfNotblank fails with content slide, pageOverlayFields is ignoredClosedJo Hasenau2015-03-20

Actions
Bug #59192: mergeIfNotBlank with FAL recordsClosed2014-05-28

Actions
Feature #35273: l10n_mode option mergeIfNotBlank should handle empty ids correctlyClosed2012-03-27

Actions
Task #78745: Get rid of localizationMode of TCA type inlineClosed2016-11-18

Actions
Bug #66206: l10n_mode mergeIfNotBlank does not work for in specific Mapping configuration (inline / direct mapping - no ObjectStorage)Closed2015-04-01

Actions
Feature #78169: Add field for the record translation mode (connected vs free)ClosedTymoteusz Motylewski2016-10-07

Actions
Feature #79658: Introduce allowLanguageSynchronizationClosed2017-02-07

Actions
Actions #1

Updated by Oliver Hader about 7 years ago

  • Description updated (diff)
Actions #2

Updated by Andreas Allacher about 7 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)

Actions #3

Updated by Susanne Moog about 5 years ago

  • Status changed from New to Closed

I'm closing the umbrella issue for version 8 but leaving the one leftover subtask open for now.

Actions

Also available in: Atom PDF