Bug #33592: Moved translated content elements are in wrong colpos - TYPO3 Core - TYPO3 Forge

Custom queries

Accessibility
Easy tasks
Forge Triage
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
My open issues
No feedback within 90 days
Open Bugs
Open issues of 10
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (2)

Stanislas Rolland
Stefan Neufeind

Actions

Copy link

Bug #33592

closed

Moved translated content elements are in wrong colpos

Added by Georg Ringer almost 13 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Workspaces

Target version:

Start date:

2012-02-01

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

4.7

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

Imagine 2 pages, both with a page_language_overlay and a contentelement with a language overlay.

If a content element in sys_language=0 is moved to the 2nd page, the page module shows both new content elements in sys_language = 0. If the one content element which has been moved and is a translation, is opend, then english is selected as language (so this is correct).

IMO there are 2 possible places where this can be fixed:
- Adopt the page module, imo the place is in tx_cms_layout.php
- or better idea: a moved placeholder should not loose its colPos

Related issues 1 (0 open — 1 closed)

Has duplicate TYPO3 Core - Bug #33594: Missing argument 4 for t3lib_TCEmain::moveL10nOverlayRecords(), called in ...version\class.tx_version_tcemain.php on line 1376

Closed

2012-02-01

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Georg Ringer almost 13 years ago

oh sorry, its about the sys_language_uid

the record with info "MOVE-TO PLACEHOLDER for #5610" should also have the sys_language_uid of the original and not 0

Actions

Copy link

Updated by Stefan Neufeind almost 13 years ago

Could it be this is related to #32967 which aims to fix an issue with colPos on publish? For that there is a patch in gerrit already. Please have a look.

Actions

Copy link

Updated by Georg Ringer almost 13 years ago

no sorry it is about the sys_language_uid.

how to test:

Go to live workspace and create 2 pages, on both a content element
(Still in live) translate pages + content elements
Switch to draft ws
cut one one content element and paste it after the another one at the other page
you will see that the translated content element got moved too (which is correct) but the translated content element is shown in default language!