Issue Bug Resolved

#106665translation button available but no elements to translate (with 3 languages)

David Menzel 05/07/25, 14:39 updated 09/23/26, 17:20

Description

I have a siteconfig with 3 languages (id:language): 0:de, 1:en and 3:cs (Czech)

Steps to reproduce:
1. Create a blank page for German and after that localize the page to English and Czech.
2. On the German page create a Text&Media element.
3. Localize the content element to English and Czech.

On the Czech column there is still the translate button but there are no unlocalized elements.
In step 3 of the localization process you’ll see an empty window with no elements and after that a spinner which does not end.
The only way to cancel the process is to reload the backend.

Tested in TYPO3 12.2.28 with PHP 8.2.28

Reviews 2

Files 3

History 611

  1. David Menzel commented <span data-processor="relativetime" data-value="2025-05-07T14:40:22+00:00" > 05/07/25, 14:40 </span>

    correction: Tested in TYPO3 12.4.28 with PHP 8.2.28

  2. Georg Ringer commented and changed status New Accepted TYPO3 Version 12 13 <span data-processor="relativetime" data-value="2025-05-26T19:42:20+00:00" > 05/26/25, 19:42 </span>

    confirmed also for 14

    problem is IMHO that l10n_source is checked in \TYPO3\CMS\Backend\View\BackendLayout\ContentFetcher::getTranslationData but not l10n_parent.

    adding the unset

    if ((int)$contentElement['l18n_parent'] > 0) {
                        $languageTranslationInfo['hasTranslations'] = true;
                        $languageTranslationInfo['mode'] = 'connected';
                        unset($untranslatedRecordUids[(int)$contentElement['l18n_parent']]);
                    }

    fixes it

  3. Gerrit Code Review pushed patch set 1 for main to change 89554 status Accepted Under Review <span data-processor="relativetime" data-value="2025-05-27T05:37:29+00:00" > 05/27/25, 05:37 </span>

  4. Mathias Stieger commented <span data-processor="relativetime" data-value="2026-01-26T08:59:27+00:00" > 01/26/26, 08:59 </span>

    Georg Ringer wrote in #note-2:
    > confirmed also for 14
    >
    > problem is IMHO that l10n_source is checked in \TYPO3\CMS\Backend\View\BackendLayout\ContentFetcher::getTranslationData but not l10n_parent.
    >
    > adding the unset
    > […]
    >
    > fixes it

    We’ve also noticed this in 13, I see there is already a fix for 14, but will this also be patched in older versions (13,12)?

  5. Martin Schulz commented <span data-processor="relativetime" data-value="2026-07-16T13:51:35+00:00" > 07/16/26, 13:51 </span>

    For me the bugfix is not working properly in the following scenario (13.4):
    1. Create default language page with one content element
    2. Create page translation for lang 1
    3. Create page translation for lang 2
    4. Click “Translate” on lang:1 page > not asking for origin language > creates translation for content elements, based on lang:0 > no more “Translate” button after that > ok
    5. Click “Translate” on lang:2 page > asks for origin language > select lang:1 -> creates translation for content element based on lang:1

    ==> broken “Translate” button is still there event with the suggested bugfix

  6. Georg Ringer commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-23T17:20:11+00:00" > 09/23/26, 17:20 </span>

    Applied in changeset commit:5b0682d06e0c1822fe79df30b5645e1bd589f838.