Issue Bug Under Review

#92377Broken sorting if translating content elements from non-default lang in workspace

Christian Kuhn 09/22/20, 22:19 updated 11/18/26, 19:15

Description

Setup:
Site with languages:
  • default lang english
  • 1. lang dansk
  • 2. lang german
LIVE:
  • Create page ‘test’
  • Add content element with header ‘1’ in normal column in default lang
  • Create page translation to dansk
  • Create page translation to german
  • Page module “translate” button for dansk: translate the default lang element to dansk
  • Page module “translate” button for german: translate the dansk (!!!) element “[Translate to dansk] 1” to german, so it becomes “[Translate to german][Translate to dansk] 1”
Go to workspace:
  • Add content element with header ‘2’ in normal column in default lang below element 1
  • Page module “translate” button for dansk: translate the element “2” to dansk
  • Page module “translate” button for german: translate the element “2” to german

-> In german, the order of the 2 content elements is changed: 2 is first one, 1 is second one. In dansk, this is 1 first, then 2, in default lang, too. So somehow the order is confused.

This only happens if in live, element 1 has been derived in german from dansk, if it has been derived from default lang, the issue does not pop up in workspace.

Reviews 2

History 13

  1. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2022-08-04T07:25:02+00:00" > 08/04/22, 07:25 </span>

    As far as I can see this still affects TYPO3 10.4.31 but is no more reproducible on 11.5.13 or 12.0.0-dev (latest master)