Project

General

Profile

Actions
Copy link

Bug #81753

open

Content element translations dissapear in page module after move to another column

Added by Markus Goldbach over 7 years ago. Updated 4 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2017-06-30
Due date:
% Done:

0%

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

Description

If the PageTS option mod.web_layout.defLangBinding is activated and you move a content element to another column the translation dissapear in the page module.
In the list module the translation is still there and connected to the parent element.

In the frontend the translation is shown on the correct column.

Exspected behavior:
If I move a content element to another column the related translations were moved to the same column, too.

Reason is that the column of the translation isn't changed, so the translation is interpreted as standalone and won't be show, because the option defLangBinding is activated and show only translation with parent elements.

Steps to reproduce:
  • activated the PageTS option mod.web_layout.defLangBinding
  • create a page and translate it
  • create a content element and create a translate it by using the

Related issues 4 (1 open — 3 closed)

Related to TYPO3 Core - Bug #21161: Problem with moved translated content elements (wrong column)AcceptedJo Hasenau2010-08-10

Actions
Related to TYPO3 Core - Bug #73732: Wrong colPos for copied content elements with defLangBinding = 1Closed2016-02-29

Actions
Related to TYPO3 Core - Bug #62550: activated defLangBinding: Content Elements that exist only in translation are not displayed at allClosed2014-10-30

Actions
Related to TYPO3 Core - Bug #93703: Having an unused content element in Page module using the language mode and deflangbinding crashes the backendClosed2021-03-11

Actions
Actions
Copy link

Also available in: Atom PDF