Bug #71586
closed
Moving content in non-default-language broken
0%
Description
In the page-module, using "Column"-mode it is not possible to move content of a non-default-language.
1) Drag-n-drop is disabled in that column.
2) Context-menu contains a "move element" but will then offer new destinations of the default-language. If you still try to move it that content will not show up in the column anymore. (One way to still "rescue" is through the List-module then.)
Updated by TO_Webmaster no-lastname-given about 9 years ago
For me, this was already not working correctly in 6.2, but it is even more broken in 7 LTS. Please fix it soon, it makes a multilingual setup almost unusable.
Updated by ToM no-lastname-given over 8 years ago
mod.web_layout.allowInconsistentLanguageHandling = 1 fixed it for me!
Updated by Riccardo De Contardi over 7 years ago
- Status changed from New to Closed
This behavior in TYPO3 7.6 is intended.
If the elements within the second language are the result of a “Translation” it should not be possible to move them; it is possible if they are “Copies” - see my answer here: http://stackoverflow.com/questions/43886183/cannot-drag-and-drop-content-elements-in-backend-after-update-to-typo3-7-6/
In TYPO3 7.6 the context menu in page>languages wrongly allows you to move elements, because doing so, they fall back to the main language.
In TYPO3 8 this misleading option has been removed.
I think I can safely close this issue, as TYPO3 7.6 is in its “priority bugfix” lifecycle phase.
If you think that this is the wrong decision please reopen it or open a new issue with a reference to this one. Thank you.