#65859Support l10n_mode in extbase
Description
Intro
Currently extbase lacks support for l10n_mode.
See #62921 for a lengthy discussion of the background. From my point of view support for l10n_mode must explicitly be enabled/added in extbase, that’s why I duplicated #62921 here.
Use Case
As Developer I want to be able to assign a relation on a record in the default translation that must not be changed in the translation of the record.
When I set l10n_mode=exclude in $TCA
When I use the \TYPO3\CMS\Extbase\Persistence\QueryInterface to lookup records by a category
Then I expect to find translated records in the Frontend
//$TCA
'faculty' => array(
'exclude' => 0,
'l10n_mode' => 'exclude',
'l10n_display' => 'hideDiff,defaultAsReadonly',
'label' => 'LLL:EXT:luhjobs/Resources/Private/Language/locallang_db.xlf:tx_luhjobs_domain_model_vacancy.faculty',
'config' => array(
'type' => 'select',
'foreign_table' => 'tx_luhjobs_domain_model_faculty',
'foreign_table_where' => 'AND tx_luhjobs_domain_model_faculty.sys_language_uid IN (-1,0)',
'items' => array(
array('',''),
),
'minitems' => 1,
'maxitems' => 1,
),
),
// QueryInterface
$constraints[] = $query->equals('faculty', $uid);
// resulting SQL(relevant parts only) in case of Frontend with ?L=1
tx_luhjobs_domain_model_vacancy.type = '19' AND tx_luhjobs_domain_model_vacancy.intern = 0
)
AND
(
tx_luhjobs_domain_model_vacancy.sys_language_uid IN (1,-1)
OR
(
tx_luhjobs_domain_model_vacancy.sys_language_uid=0 AND tx_luhjobs_domain_model_vacancy.uid NOT IN
(
SELECT tx_luhjobs_domain_model_vacancy.l10n_parent FROM tx_luhjobs_domain_model_vacancy WHERE tx_luhjobs_domain_model_vacancy.l10n_parent>0 AND tx_luhjobs_domain_model_vacancy.sys_language_uid=1 AND tx_luhjobs_domain_model_vacancy.deleted=0
)
)
)
This does miss the translated records as they have faculty=0 due to the l10n_mode=exclude setting in $TCA
Reviews 3
Related issues 6
- Bug #62921l10n_mode with relations does not work in Extbase
- Bug #82657l10n_mode exclude ignored in repository
- Bug #88452TCA field type inline ignores l10n_mode "exclude"
- Bug #90430Language handling of bidirectional mm selects is not consitent.
- Story #101566Extbase related translation issues
- Epic #108986Improve MM handling in TYPO3 Core related to language + workspace concepts
History 1533
Show 8 earlier messages
-
Peter Niederlag changed description <span data-processor="relativetime" data-value="2015-03-20T09:42:04+00:00" > 03/20/15, 09:42 </span>
-
Peter Niederlag changed description <span data-processor="relativetime" data-value="2015-03-20T09:48:56+00:00" > 03/20/15, 09:48 </span>
-
Riccardo De Contardi changed category <span data-processor="relativetime" data-value="2015-12-05T17:53:31+00:00" > 12/05/15, 17:53 </span>
-
Riccardo De Contardi changed category <span data-processor="relativetime" data-value="2017-10-01T12:18:49+00:00" > 10/01/17, 12:18 </span>
-
Benni Mack commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2018-07-19T08:48:24+00:00" > 07/19/18, 08:48 </span> -
Johannes Rebhan commented <span data-processor="relativetime" data-value="2018-09-25T13:10:49+00:00" > 09/25/18, 13:10 </span>
@Benni
Sadly it’s not fixed with v8. I’ve run into the same problem where I have an object which has categories in the base language, then I translate said object with extbase, assign the original object and save it.
The categories field is set as l10n_mode = exclude, but it doesn’t work when using core extbase. It seems to work in the backend, because when I edit the translated object (no categories selection shown) and save it – without changing anything – the values are copied. When I do the same in extbase by loading the translated object through a querybuilder query (can’t get it any other way in the backend/commandcontrollers), which is then mapped to the object by using DataMapper, it doesn’t apply those TCA settings after I’ve stored with through a repository update().
-
Tymoteusz Motylewski commented <span data-processor="relativetime" data-value="2018-11-03T19:45:05+00:00" > 11/03/18, 19:45 </span>
So querying works but data is not propagated when saving a record through extbase?
This is because extbase doesnt use datahandler for storing values. -
Benni Mack changed Related to #82657 <span data-processor="relativetime" data-value="2020-05-12T21:28:05+00:00" > 05/12/20, 21:28 </span>
-
Anonymous commented <span data-processor="relativetime" data-value="2021-05-14T15:14:23+00:00" > 05/14/21, 15:14 </span>
Still a thing in 10.4.16
-
Riccardo De Contardi changed status
Needs FeedbackNew TYPO3 Version6.210 <span data-processor="relativetime" data-value="2021-09-15T19:27:04+00:00" > 09/15/21, 19:27 </span> -
Jan Kornblum changed Related to #90430 <span data-processor="relativetime" data-value="2021-09-16T19:35:51+00:00" > 09/16/21, 19:35 </span>
-
Jan Kornblum commented <span data-processor="relativetime" data-value="2022-02-03T22:50:09+00:00" > 02/03/22, 22:50 </span>
Tymoteusz Motylewski wrote in #note-7:
> So querying works but data is not propagated when saving a record through extbase?Regarding querying, possibly still a (minor) bug: Lets have “product” with two relations “type” (n:1) and “categories” (m:m). For all records (products, types, categories) a translation (L=1) exists.
Now products are queried using the following, while L=1 (and fallbackType=fallback):
// MM - Works fine $query->contains('categories', $category)// N:1 - Does NOT work (no records fetched) $query->equals('type', $type) // N:1 - DOES work instead (why?) $query->equals('type', $type->getUid())Seems there is something missing regarding n:1 relations, when the operand is localized.
-
Astrid Haubold changed Related to #101566 <span data-processor="relativetime" data-value="2023-11-01T18:20:45+00:00" > 11/01/23, 18:20 </span>
-
Gerrit Code Review pushed patch set 18 for main to change 67172 status
NewUnder Review <span data-processor="relativetime" data-value="2024-03-17T11:43:00+00:00" > 03/17/24, 11:43 </span> -
Gerrit Code Review pushed patch set 19 for main to change 67172 <span data-processor="relativetime" data-value="2024-03-17T12:02:58+00:00" > 03/17/24, 12:02 </span>
-
Gerrit Code Review pushed patch set 20 for main to change 67172 <span data-processor="relativetime" data-value="2024-03-17T12:23:53+00:00" > 03/17/24, 12:23 </span>
-
Gerrit Code Review pushed patch set 21 for main to change 67172 <span data-processor="relativetime" data-value="2024-03-17T12:24:36+00:00" > 03/17/24, 12:24 </span>
-
Gerrit Code Review pushed patch set 22 for main to change 67172 <span data-processor="relativetime" data-value="2024-03-24T09:07:11+00:00" > 03/24/24, 09:07 </span>
-
Gerrit Code Review pushed patch set 23 for main to change 67172 <span data-processor="relativetime" data-value="2024-03-24T13:42:37+00:00" > 03/24/24, 13:42 </span>
-
Gerrit Code Review pushed patch set 24 for main to change 67172 <span data-processor="relativetime" data-value="2024-03-24T14:24:28+00:00" > 03/24/24, 14:24 </span>
-
Gerrit Code Review pushed patch set 25 for main to change 67172 <span data-processor="relativetime" data-value="2024-03-24T14:41:52+00:00" > 03/24/24, 14:41 </span>
-
Gerrit Code Review pushed patch set 26 for main to change 67172 <span data-processor="relativetime" data-value="2024-10-18T13:41:09+00:00" > 10/18/24, 13:41 </span>
-
Benni Mack changed Related to #88452 <span data-processor="relativetime" data-value="2025-04-02T07:13:43+00:00" > 04/02/25, 07:13 </span>
-
Benni Mack changed Related to #108986 <span data-processor="relativetime" data-value="2026-02-15T17:19:00+00:00" > 02/15/26, 17:19 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 95445 <span data-processor="relativetime" data-value="2026-08-27T06:43:32+00:00" > 08/27/26, 06:43 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 95445 <span data-processor="relativetime" data-value="2026-10-08T07:58:44+00:00" > 10/08/26, 07:58 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 95445 <span data-processor="relativetime" data-value="2026-10-08T09:07:09+00:00" > 10/08/26, 09:07 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 95445 <span data-processor="relativetime" data-value="2026-10-08T09:11:23+00:00" > 10/08/26, 09:11 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 95445 <span data-processor="relativetime" data-value="2026-10-10T19:34:47+00:00" > 10/10/26, 19:34 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 95445 <span data-processor="relativetime" data-value="2026-10-10T20:08:47+00:00" > 10/10/26, 20:08 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 95445 <span data-processor="relativetime" data-value="2026-10-18T13:22:49+00:00" > 10/18/26, 13:22 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 95445 <span data-processor="relativetime" data-value="2026-10-18T13:39:28+00:00" > 10/18/26, 13:39 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 95445 <span data-processor="relativetime" data-value="2026-11-11T09:13:58+00:00" > 11/11/26, 09:13 </span>
Peter, I guess this is now fixed with TYPO3 v8, can you verify this?