Bug #81753

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

Added by Markus Goldbach about 5 years ago. Updated over 3 years 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

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 backendAccepted2021-03-11

Actions
#1

Updated by Markus Goldbach about 5 years ago

  • Description updated (diff)
#2

Updated by Gerrit Code Review about 5 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/53367

#3

Updated by Markus Goldbach about 5 years ago

  • Related to Bug #21161: Problem with moved translated content elements (wrong column) added
#4

Updated by Riccardo De Contardi almost 5 years ago

  • Related to Bug #73732: Wrong colPos for copied content elements with defLangBinding = 1 added
#5

Updated by Riccardo De Contardi almost 5 years ago

  • Related to Bug #62550: activated defLangBinding: Content Elements that exist only in translation are not displayed at all added
#6

Updated by Benni Mack over 4 years ago

  • Sprint Focus set to On Location Sprint
#7

Updated by Mathias Brodala over 4 years ago

  • Sprint Focus deleted (On Location Sprint)
#8

Updated by Susanne Moog about 4 years ago

  • Status changed from Under Review to New

This needs more discussion. With the latest bug fixes mod.web_layout.defLangBinding shows the elements again, what's missing for this issue is more a conceptional problem: shall the element move with its language parent?

#9

Updated by Riccardo De Contardi over 3 years ago

Susanne Moog wrote:

This needs more discussion. With the latest bug fixes mod.web_layout.defLangBinding shows the elements again [...]

I tried to reproduce the problem on the latest master (10.0.0 dev), and it is still present AFAICS

Steps to reproduce it

Prerequisites

  • TYPO3 with at least 2 languages
  • a page with two columns (let's say "0" and "1")

Test

1) create a page
2) create two content elements in a column (0)
3) translate them in "Translate Mode" (important, the issue is visible only in this case)
4) Use the "Languages" view of the page module
5) Move with drag and drop one element on the other column (1)

Results with mod.web_layout.defLangBinding = 0

The translated element is not moved on the other column, and is visible on the column

Results with mod.web_layout.defLangBinding = 1

The translated element is not moved on the other column, and is not visible on the column, it can only be seen in List module

h3.Note

It is strange that, as stated on the issue description, in frontend the elements are shown in the correct column,

but

As far as I have seen in both cases, if you edit the translated element that has been moved, it still has the original colPos (0)

#10

Updated by Riccardo De Contardi over 3 years ago

Susanne Moog wrote:

This needs more discussion. With the latest bug fixes mod.web_layout.defLangBinding shows the elements again [...]

I tried to reproduce the problem on the latest master (10.0.0 dev), and it is still present AFAICS

Steps to reproduce it

Prerequisites

  • TYPO3 with at least 2 languages
  • a page with two columns (let's say "0" and "1")

Test

1) create a page
2) create two content elements in a column (0)
3) translate them in "Translate Mode" (important, the issue is visible only in this case)
4) Use the "Languages" view of the page module
5) Move with drag and drop one element on the other column (1)

Results with mod.web_layout.defLangBinding = 0

The translated element is not moved on the other column, and is visible on the column

Results with mod.web_layout.defLangBinding = 1

The translated element is not moved on the other column, and is not visible on the column, it can only be seen in List module

h3.Note

It is strange that, as stated on the issue description, in frontend the elements are shown in the correct column,

but

As far as I have seen in both cases, if you edit the translated element that has been moved, it still has the original colPos (0)

As I wrote here https://forge.typo3.org/issues/21161#note-5 it seems that only the colPos of the original language is considered in frontend

#11

Updated by Markus Klein over 1 year ago

  • Related to Bug #93703: Having an unused content element in Page module using the language mode and deflangbinding crashes the backend added

Also available in: Atom PDF