Bug #81753
open
Content element translations dissapear in page module after move to another column
0%
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.
- 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
Updated by Gerrit Code Review almost 7 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
Updated by Markus Goldbach almost 7 years ago
- Related to Bug #21161: Problem with moved translated content elements (wrong column) added
Updated by Riccardo De Contardi over 6 years ago
- Related to Bug #73732: Wrong colPos for copied content elements with defLangBinding = 1 added
Updated by Riccardo De Contardi over 6 years ago
- Related to Bug #62550: activated defLangBinding: Content Elements that exist only in translation are not displayed at all added
Updated by
Updated by Mathias Brodala about 6 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Susanne Moog almost 6 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?
Updated by Riccardo De Contardi about 5 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)
Updated by Riccardo De Contardi about 5 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
Updated by Markus Klein about 3 years ago
- Related to Bug #93703: Having an unused content element in Page module using the language mode and deflangbinding crashes the backend added