Project

General

Profile

Actions

Bug #12328

closed

Reordering localized content causes translation to display under default language

Added by Felix Buenemann over 13 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2011-01-17
Due date:
% Done:

0%

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

Description

If you change the position of content that has linked localizations, those localizations will be displayed in the column of the default language in page module columns and languages view.
After publishing the changes, the language is correct again.

Eg. if you reorder element a in column "German (default language)" of languages view, then your translation a will also be displayed in column German instead of in column English, although the language flags still indicate that it is actually translated content.

This seems to be related or maybe a duplicate of this old bug: http://bugs.typo3.org/view.php?id=9321

Only I'm on TYPO3 4.4.6 and the old report is from 4.2.1 / September 2008.


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #16845: Incorrect values of colPos, sys_language_uid and sorting after moving records in web > listClosedStanislas Rolland2007-01-09

Actions
Actions #1

Updated by Tolleiv Nietsch over 13 years ago

Feel free to review RFC #4759 in the core list

Actions #2

Updated by Tolleiv Nietsch over 13 years ago

  • Status changed from New to On Hold
Actions #3

Updated by Ernst Went over 12 years ago

In TYPO3 4.5.2 the problem still exists.
Reordering an element in the default language creates a MOVE-TO PLACEHOLDER for both the translated element and the default language element. And the sys_language_uid of the translated element is set to 0, therefore it is displayed in the default language.

Actions #4

Updated by Tolleiv Nietsch over 12 years ago

  • Status changed from On Hold to Needs Feedback
  • TYPO3 Version set to 4.6
Actions #5

Updated by Ernst Went over 12 years ago

Yes, it is. The last update of Dani describes the same situation.

Actions #6

Updated by Michael Stucki over 10 years ago

  • Category changed from Bugs to Workspaces
Actions #7

Updated by Michael Stucki over 10 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions #8

Updated by Alexander Opitz about 10 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No

Close as duplicate of #16845

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF