#107790Utilize language domain mapping in Modules.php
Description
With #93334 I would expect the following notations to work, however none of them works:
return [
'blog_example' => [
'labels' => 'LLL:blog_example.module.mod',
/// 'labels' => 'blog_example.module.mod',
'extensionName' => 'BlogExample',
...
],
];
However none of these notations works, only using the complete path works
Reviews 5
- main 91552[TASK] Add basic XLIFF validation / linting
- main 91566[TASK] Add "debug:backend:modules", "debug:backend:routes" commands
- main 91550[TASK] Migrate module labels to new short label domain
- main 91553[TASK] Rename second-level module "view" to "preview"
- main 91169[TASK] Add new syntax for referencing labels for modules
Related issues 3
History 816
-
Lina Wolf changed Related to #93334 <span data-processor="relativetime" data-value="2025-10-20T11:01:00+00:00" > 10/20/25, 11:01 </span>
-
Georg Ringer commented <span data-processor="relativetime" data-value="2025-10-20T11:21:38+00:00" > 10/20/25, 11:21 </span>
this references currently a language file with magic keys and should be transformed into label + description or so.
I don’t expect a mapping to language files there via the new features
-
Lina Wolf commented <span data-processor="relativetime" data-value="2025-10-20T11:38:15+00:00" > 10/20/25, 11:38 </span>
When Updating the blog_example I was expecting that all occurences of LLL:EXT:blog_example/Resources/Private/Language/Module/locallang_mod.xlf could be replaced. However I would agree that being able to use any language string for title and description, following practices from, for example TCA would even be better
-
Gerrit Code Review pushed patch set 1 for main to change 91169 status
NewUnder Review <span data-processor="relativetime" data-value="2025-10-20T15:16:36+00:00" > 10/20/25, 15:16 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91169 <span data-processor="relativetime" data-value="2025-11-05T15:39:23+00:00" > 11/05/25, 15:39 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 91169 <span data-processor="relativetime" data-value="2025-11-10T21:32:56+00:00" > 11/10/25, 21:32 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 91169 <span data-processor="relativetime" data-value="2025-11-11T00:29:00+00:00" > 11/11/25, 00:29 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 91169 <span data-processor="relativetime" data-value="2025-11-11T07:43:34+00:00" > 11/11/25, 07:43 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 91169 <span data-processor="relativetime" data-value="2025-11-11T09:37:14+00:00" > 11/11/25, 09:37 </span>
-
Garvin Hicking changed Related to #108047 <span data-processor="relativetime" data-value="2025-11-11T13:42:08+00:00" > 11/11/25, 13:42 </span>
-
Garvin Hicking changed Related to #108045 <span data-processor="relativetime" data-value="2025-11-11T13:42:24+00:00" > 11/11/25, 13:42 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 91169 <span data-processor="relativetime" data-value="2025-11-11T13:46:08+00:00" > 11/11/25, 13:46 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 91169 <span data-processor="relativetime" data-value="2025-11-11T15:13:12+00:00" > 11/11/25, 15:13 </span>
-
Benni Mack commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-11-11T17:40:08+00:00" > 11/11/25, 17:40 </span>Applied in changeset commit:5da5e001bd7097bdfeb47a57ace87d8d0a5337b6.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T12:04:35+00:00" > 12/02/25, 12:04 </span>
Only the following works: