Issue Bug New Orphaned

#93872Localization problems (for tt_content) if source is a non-default language

Sandra Leitner 04/07/21, 13:17 updated 04/07/21, 13:17

Description

Starting point
  1. Create page DE
  2. Create the content elements DE.A and DE.B on the page DE
  3. Create page ES
  4. Translate content elements from page DE to ES (connected mode) -> ES.A and ES.B
  5. Create page CL
  6. Translate content elements from page ES to CL (connected mode) -> CL.A and CL.B
PROBLEM 1:
  • Create a third content element DE.C on page DE
  • The translate button is now displayed on the CL page, but if you press it, no content elements are available in the popup and the process fails while localization
  • Problem can only be solved if the content element DE.C is translated to ES before and then it can be translated for the CL page
  • If there are many languages ​​in a project, it is impossible to know which language you initially used for Localization and there is no indication which language has been used as the source language!
PROBLEM 2:
  • Translate element DE.C directly for page CL (Edit Element DE.C on page DE and select the option “CL [NEW]” in the top selection box)
  • Delete element CL.B on page CL
  • If you click on the translate button on the CL page, ALL content elements of the default language are listed for translation even though they have already been translated

The problem also occurs in TYPO3 version 9 and 8.

Reviews 0

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

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Localization problems (for tt_content) if source is a non-default language Resolves: #93872 Releases: main