#93025File metadata are not translated in the free mode
Description
Problem:
File metadata are by default retrieved in a default language or “All languages” (see MetaDataRepository). This makes it impossible to get a translation when the fallbackType is set to free.
Steps to reproduce:
- Create an empty TYPO3
- Create a site with at least 2 languages and set fallbackType to free
- Add a file with metadata translations
- Show file metadata in non-default language in the frontend
Result:
Metadata are always in a default language
Reviews 2
Related issues 1
History 1534
Show 69 earlier messages
-
Michal Majernik changed description <span data-processor="relativetime" data-value="2020-12-08T08:46:45+00:00" > 12/08/20, 08:46 </span>
-
ondro no-lastname-given commented <span data-processor="relativetime" data-value="2021-06-15T14:17:04+00:00" > 06/15/21, 14:17 </span>
-
ondro no-lastname-given commented <span data-processor="relativetime" data-value="2021-06-16T07:37:13+00:00" > 06/16/21, 07:37 </span>
ondro no-lastname-given wrote in #note-2:
> Hello Michal,
>
> Have you found a solution for this, we’re struggling with the same bug as wellWe’ve used exiting event listener in MetaDataRepository to fix this issue.
Looks like problem is in query performed in findByFileUid https://github.com/TYPO3/TYPO3.CMS/blob/7aad9f6dea9246a1cc64f1b076e106605db3e04c/typo3/sysext/core/Classes/Resource/Index/MetaDataRepository.php#L105 where only sys_language_uid in [0,-1] are fetched -
Alexander Stehlik commented <span data-processor="relativetime" data-value="2021-10-15T10:57:30+00:00" > 10/15/21, 10:57 </span>
Hi there,
for everyone having this problem in TYPO3 9:
You can checkout https://github.com/Intera/typo3-extension-storagefixes which contains a workaround.
Cheers
Alex -
Simon Gilli changed Related to #52816 <span data-processor="relativetime" data-value="2021-10-27T20:07:08+00:00" > 10/27/21, 20:07 </span>
-
Anonymous commented <span data-processor="relativetime" data-value="2021-10-28T09:33:27+00:00" > 10/28/21, 09:33 </span>
Still present in TYPO3 11.5.1
-
Gerrit Code Review pushed patch set 1 for master to change 72015 status
NewUnder Review <span data-processor="relativetime" data-value="2021-10-31T18:22:17+00:00" > 10/31/21, 18:22 </span> -
Gerrit Code Review pushed patch set 2 for master to change 72015 <span data-processor="relativetime" data-value="2021-10-31T18:34:12+00:00" > 10/31/21, 18:34 </span>
-
Gerrit Code Review pushed patch set 3 for master to change 72015 <span data-processor="relativetime" data-value="2021-10-31T19:31:40+00:00" > 10/31/21, 19:31 </span>
-
Gerrit Code Review pushed patch set 4 for master to change 72015 <span data-processor="relativetime" data-value="2021-10-31T19:35:32+00:00" > 10/31/21, 19:35 </span>
-
Gerrit Code Review pushed patch set 5 for master to change 72015 <span data-processor="relativetime" data-value="2021-11-02T13:27:33+00:00" > 11/02/21, 13:27 </span>
-
Gerrit Code Review pushed patch set 6 for master to change 72015 <span data-processor="relativetime" data-value="2021-11-18T10:42:34+00:00" > 11/18/21, 10:42 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 72015 <span data-processor="relativetime" data-value="2021-11-29T14:02:44+00:00" > 11/29/21, 14:02 </span>
-
Vladimir Falcon commented <span data-processor="relativetime" data-value="2022-07-13T07:02:14+00:00" > 07/13/22, 07:02 </span>
I was wondering what can I do to help you to get this patch merge in to the TYPO3 Core. I am already using it in TYPO3 V10 (PSR-14) and it works exactly as expected. Please let me know if I can be of any help.
-
Anonymous commented <span data-processor="relativetime" data-value="2022-07-13T07:08:50+00:00" > 07/13/22, 07:08 </span>
You can review the patch and tell that you verified the functionality.
Aynway, the patch contains an unresolved merge conflict. I don’t know what else is needed here to getting this merged… -
Gerrit Code Review pushed patch set 8 for main to change 72015 <span data-processor="relativetime" data-value="2023-05-03T09:16:24+00:00" > 05/03/23, 09:16 </span>
-
Benni Mack commented and changed status
Under ReviewAccepted <span data-processor="relativetime" data-value="2023-07-31T13:42:22+00:00" > 07/31/23, 13:42 </span>Patch wasnt updated in the past year, so the issue is changed to accepted.
-
Bernhard Eckl commented <span data-processor="relativetime" data-value="2024-01-09T12:35:33+00:00" > 01/09/24, 12:35 </span>
Same issue here with TYPO3 11. I applied the patch for FileMetadataOverlayAspect.php: works. Please apply the patch to at least TYPO3 11 soon.
-
Yohann CERDAN commented and changed TYPO3 Version
1012 <span data-processor="relativetime" data-value="2024-09-10T09:39:28+00:00" > 09/10/24, 09:39 </span>Same issue here with TYPO3 12. I applied the patch for FileMetadataOverlayAspect.php and it works.
-
Yohann CERDAN changed TYPO3 Version
1210 <span data-processor="relativetime" data-value="2024-09-10T09:39:44+00:00" > 09/10/24, 09:39 </span> -
Gerrit Code Review pushed patch set 9 for main to change 72015 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2024-12-16T16:52:19+00:00" > 12/16/24, 16:52 </span> -
Gerrit Code Review pushed patch set 10 for main to change 72015 <span data-processor="relativetime" data-value="2024-12-19T20:42:08+00:00" > 12/19/24, 20:42 </span>
-
Thomas Kühnel commented <span data-processor="relativetime" data-value="2025-03-04T11:20:42+00:00" > 03/04/25, 11:20 </span>
Hej, in our case the patch doesn’t work for languages with fallback type ‘free’.
Because in the
LanguageAspectFactory::createFromSiteLanguage()the fallback type ‘free’ results in the overlay typeLanguageAspect::OVERLAYS_OFF. This constant is used in thePageRepository->getRecordOverlay()method to trigger an early return. As I understand it, it cannot work like this for the ‘free’ mode.If disabling the early return in the
PageRepository->getRecordOverlay()method it works as described.TYPO3 v12.4.27
-
Gerrit Code Review pushed patch set 11 for main to change 72015 <span data-processor="relativetime" data-value="2025-04-10T07:21:05+00:00" > 04/10/25, 07:21 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 72015 <span data-processor="relativetime" data-value="2025-04-10T08:46:18+00:00" > 04/10/25, 08:46 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 72015 <span data-processor="relativetime" data-value="2025-04-10T10:30:16+00:00" > 04/10/25, 10:30 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 72015 <span data-processor="relativetime" data-value="2025-04-10T11:33:32+00:00" > 04/10/25, 11:33 </span>
-
Gerrit Code Review pushed patch set 15 for main to change 72015 <span data-processor="relativetime" data-value="2025-04-10T11:50:38+00:00" > 04/10/25, 11:50 </span>
-
Gerrit Code Review pushed patch set 16 for main to change 72015 <span data-processor="relativetime" data-value="2025-04-10T19:25:32+00:00" > 04/10/25, 19:25 </span>
-
Gerrit Code Review pushed patch set 17 for main to change 72015 <span data-processor="relativetime" data-value="2025-04-10T20:01:51+00:00" > 04/10/25, 20:01 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 89047 <span data-processor="relativetime" data-value="2025-04-10T20:14:19+00:00" > 04/10/25, 20:14 </span>
-
Gerrit Code Review pushed patch set 2 for 13.4 to change 89047 <span data-processor="relativetime" data-value="2025-04-10T20:16:21+00:00" > 04/10/25, 20:16 </span>
-
Alexander Stehlik commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-04-10T20:30:07+00:00" > 04/10/25, 20:30 </span>Applied in changeset commit:3210414134c59d15270b1e163830a09a59c45730.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T14:33:51+00:00" > 12/02/25, 14:33 </span>
Hello Michal,
Have you found a solution for this, we’re struggling with the same bug as well