Bug #73732
closed
Wrong colPos for copied content elements with defLangBinding = 1
Added by Christian Fries about 8 years ago.
Updated over 6 years ago.
Description
TYPO3 7.6.4, mod.web_layout.defLangBinding = 1:
When you copy a translated content element in page module (language view, not columns) in the default language and paste it on the same or another page, the content element is copied (available in list module) but the assigned colPos is wrong (0).
In columns view it works as expected, also if mod.web_layout.defLangBinding = 0
Related issues
1 (1 open — 0 closed)
I can confirm this issue on TYPO3 6.2 LTS
Will this option be fixed in TYPO3 CMS 7.6?
- Related to Bug #81753: Content element translations dissapear in page module after move to another column added
Hi,
Can anyone tell me how to reproduce the problem? I have problems understanding "copy a translated content element" [...] "in the default language".
Thank you very much.
@Nicole I think I was able to reproduce it on version 7 with this setup:
1) mod.web_layout.defLangBinding = 1
2) Create a page with 2 languages (Default, language=1)
3) The page must have at least 2 columns (colPos=0, colPos=1)
4) create a content element in colPos=1
5) Switch to the "language view"
6) translate it into the 2nd language.
7) while you are still in "language view", right-click on the element in the default language and, from the context menu, click "copy"
8) select another page with 2 languages and the same backend layout
9) try to paste it into the area with colPos=1
Result: the element is pasted in the area with colPos=0
It seems solved in latest Master, can someone confirm? And test it in 8.7?
I have performed a test with a fresh system with TYPO3 8.7.8 (and Bootstrap Package) using the same procedure described on my previous comment. The result is that the copied content elements (both in standard and language=1) mantain the correct colpos when copied. So I think it it solved for 8.7.x.
Is a different test necessary?
- Status changed from New to Needs Feedback
Hi,
I tested the reported behaviour with current 8.7 develop-Branch as well as current 7.6 develop-Branch. In both versions the issue seems to be fixed. Would anyone like to verify the fix?
- Status changed from Needs Feedback to Closed
I repeated my test with 7.6.x on a fresh installation, and I was not able to reproduce the issue;
for now, I close it as it seems resolved for version 7.6.x and higher; if you think that this is the wrong decision, or experience the issue again, or that a different test should be performed, then please reopen it or open a new issue with a reference to this one. Thank you.
post scriptum
On my previous test (see comment 5), I was using EXT:gridelements, I just want to mention it.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by