Issue Bug Closed

#85535translate does not show languages to chose from, when a translated item exists

Daxboeck no-lastname-given 07/12/18, 09:00 updated 10/15/26, 18:56

Description

We see the following issue when creating translations of an element:

Given Scenario:
- we have 3 languages: default(English), Swiss German and Swiss French.
- we created content in “default” and already have translated all stuff to “Swiss German” and we work on “Swiss French”.
- we have 1 Header Element and 3 Text and Media elements in “Default” and translated to “Swiss German”.

Now the Editor is working to create “Swiss French” translations.
He takes the “Header” from Swiss German and clicks on “Swiss French[New]” above, changes the content to French and saves it.

Now he wants to get the other 3 Text and Media elements form “Default” and click on the “Translate” button.
to his annoyance, he does not get the choice to take the content from “default”.

this behavior of the “translate” button is irritating and not intuitive and in situations like above even annoying.
No matter the case, the “translate” button should always give all potential source languages as a choice.
At least, there should be a system configuration option, to chose the behaviour within a TYPO3 installation.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 3

  1. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2020-04-10T18:09:04+00:00" > 04/10/20, 18:09 </span>

    I think that this issue is still present on 10.4.0-dev (latest master) but I am not sure about how to reproduce it; I will write here the test I performed:

    Prerequisites

    - TYPO3 with three languages:
    Italian (Default); English (ID=1); French (ID=2)

    Test procedure

    1) Create a “Test” page and translate it into English and French
    2) Create four content elements in Default language
    2.1) Headline “Test 1” (Just headline)
    2.2) Text and Images “(Test 2” (Just headline and bodytext)
    2.3) Text and Images “Test 3” (Just headline and bodytext)
    2.4) Text and Images “Test 4” (Just headline and bodytext)
    3) Translate everything in English (Translate mode)

    Result (so far)

    Four elements in “English” (translate mode)

    - “Test 1 in English“
    - “Test 2 in English“
    - “Test 3 in English“
    - “Test 4 in English”

    Test

    1) Click on “Translate” button; select “translate” mode, select as “source” of translation: English and select only the Headline element (“Test 1 in English”)
    2) Result: only one element “Test 1 in French” on the page in French.
    3) Click again on “Translate” button, select “translate” mode (the only one selectable)

    Result

    You can’t select “Italian” as “Translation source”: that passage is skipped and you can only translate from the English source

    Is this the right test? Or a different one should be performed?

  2. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-15T18:56:24+00:00" > 10/15/26, 18:56 </span>

    thank you very much for this report, and sorry it sat here for so long. Your description of the editor workflow was spot on: you described exactly the
    situation that leads to pages with content translated from several different source languages. That turned out to be one of the problems the translation
    workflow rework in TYPO3 v14 set out to solve. Thanks also to Riccardo for the detailed reproduction steps back in 2020.

    What changed

    With TYPO3 v14 the localization wizard was rebuilt from scratch. Part of that rework is a deliberate consistency rule for page translations:

    • If the translated page has no content yet, the wizard offers every available language as the translation source.
    • As soon as content exists in the target language, the wizard only offers the source language(s) that content was translated from.
    • The same applies to the localization mode: the wizard only offers “Translate” or “Copy”, whichever matches the existing translations.

    The goal is to keep each page translation consistent. In connected mode, a French page whose elements come partly from German and partly from English is hard to keep in sync: when the default-language content changes, editors and integrators can no longer tell which French elements are outdated. Many of the old “my translations are mixed up” reports trace back to exactly this.

    Why this ticket is being closed

    So it’s no longer a bug in the sense of this ticket. I will close this now. If you feel this is the wrong decision, please reach out to me.

    Your second suggestion, a configuration option that allows mixing source languages on purpose, is a valid feature idea of its own. If you or anyone
    else still needs it with the new wizard, please open a new Feature ticket that describes the use case. It’s easier to discuss there than in a bug
    report from 2018.