Bug #25768
closed
Grid View: It is not possible to move a content element to another column in page/grid view
Added by Sonja Schubert about 13 years ago.
Updated almost 10 years ago.
Category:
Backend User Interface
Description
When someone uses the page/grid view it is not possible to move a content element with its all language overlay elements to another column of the grid, as there is no button for that like "cut" and then "paste into".
It is possible to change the sorting in the own column of the element, but that is not enough to change the column.
Temporary, the user has to edit the content element and then change the "column" their, which is not a good solution for the normal user.
doesn't joey work on a drag'n' drop?
Drag and drop has been added. This issues seems to be outdated.
Can be closed?
Felix Kopp wrote:
Drag and drop has been added. This issues seems to be outdated.
Can be closed?
Yes, but still does the drag'n'drop considr the column settings of the tt_content elements in the other language?
I don't think that's solved!
- Status changed from New to Needs Feedback
- TYPO3 Version changed from 4.5 to 6.0
- Complexity set to medium
Please test this again with the drag and drop in 6.x.
- % Done changed from 0 to 70
Moving between columns works with 6.2 / master
Didn't test behaviour for elements in other languages
But one has to remind that cut/copy/paste is simply a different concept than drag&drop.
On a normal modern OS you have both options available and can use the prefered one.
In TYPO3 the possibility to drag&drop a content element to another page is still missing.
- % Done changed from 70 to 0
- Is Regression set to No
This issue was about drag'n'drop on same page of an element with translated content and not about drag'n'drop handling like on the OS.
Does the original problem still exists within newer versions of TYPO3 CMS (6.1.7)?
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by