Project

General

Profile

Actions

Bug #21161

open

Problem with moved translated content elements (wrong column)

Added by Axel Kloss over 13 years ago. Updated over 2 years ago.

Status:
Accepted
Priority:
Must have
Assignee:
Category:
Localization
Start date:
2010-08-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

There is a problem if you´ve got an website with 2 or more columns and more than one language. If you shift a content element (the default lang) from one column to an other, only the default language gets the new column attribute, the translated elements holds the old column. In the frontend it doesn´t matters because only the column attribute from the default language counts (that means in FE it looks good even though in BE it is wrong).

(issue imported from #M15413)


Related issues 5 (2 open3 closed)

Related to TYPO3 Core - Task #66540: Avoid having content jump up and down when dragging elementsClosedJo Hasenau2015-04-22

Actions
Related to TYPO3 Core - Bug #72547: Moving orig tt_content records does not move translated recordsClosed2016-01-06

Actions
Related to TYPO3 Core - Bug #81753: Content element translations dissapear in page module after move to another columnNew2017-06-30

Actions
Related to TYPO3 Core - Bug #95069: Add eventDict to DragDrop JS libClosedAndreas Kienast2021-09-01

Actions
Related to TYPO3 Core - Epic #101557: Translation Handling FindingsNew2023-08-03

Actions
Actions

Also available in: Atom PDF