Bug #12328
closed
Reordering localized content causes translation to display under default language
0%
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.
Updated by Tolleiv Nietsch almost 14 years ago
Feel free to review RFC #4759 in the core list
Updated by Tolleiv Nietsch almost 14 years ago
- Status changed from New to On Hold
Updated by Ernst Went about 13 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.
Updated by Tolleiv Nietsch almost 13 years ago
- Status changed from On Hold to Needs Feedback
- TYPO3 Version set to 4.6
Duplicate of http://forge.typo3.org/issues/16845 - right?
Updated by Ernst Went almost 13 years ago
Yes, it is. The last update of Dani describes the same situation.
Updated by Michael Stucki almost 11 years ago
- Category changed from Bugs to Workspaces
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Updated by Alexander Opitz over 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.