Project

General

Profile

Actions

Bug #94397

closed

Translation Button is shown in connected mode if l10n_source differs from l18n_parent

Added by André Buchmann over 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2021-06-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

If I translate a content element (in the backend) not from the standard language but from a translation, it always shows the translation button. So the issue is with translating from a translation where the `l18n_parend` is not equal to `l10n_source`. (See more details here: #92937-3)

Example translated with the TYPO3 backend translation modal:
EN -> DA -> DE = Translation button is shown
EN -> DA = No translation button is shown
EN -> DE = Also no translation button is shown

By clicking the button again the wizard opens, finds nothing to translate and it will circle endlessly in the last step.

Tested with TYPO3 10.4.17 & 11.2.dev


Files

clipboard-202106221058-9drz9.png (90.3 KB) clipboard-202106221058-9drz9.png André Buchmann, 2021-06-22 08:58

Related issues 2 (2 open0 closed)

Related to TYPO3 Core - Bug #92937: Translation wizard of tt_content having l10n_source = 0 shows too many itemsUnder Review2020-11-26

Actions
Is duplicate of TYPO3 Core - Bug #97763: Translation Button shown eventhough already translatedUnder ReviewJo Hasenau2022-06-13

Actions
Actions #1

Updated by André Buchmann over 3 years ago

  • Description updated (diff)
Actions #2

Updated by Riccardo De Contardi over 3 years ago

  • Related to Bug #92937: Translation wizard of tt_content having l10n_source = 0 shows too many items added
Actions #3

Updated by Riccardo De Contardi over 3 years ago

  • Category set to Localization
Actions #4

Updated by Nikita Hovratov over 2 years ago

  • Is duplicate of Bug #97763: Translation Button shown eventhough already translated added
Actions #5

Updated by Nikita Hovratov over 2 years ago

  • Status changed from New to Closed

I accidentally created a new ticket with the same issue and already pushed a patchset there. I will close this ticket then.

Actions

Also available in: Atom PDF