Bug #46749

Drag'n'drop child elements inside Gridelements + Workspaces

Added by Maik Peuser over 2 years ago. Updated over 2 years ago.

Status:Rejected Start date:2013-03-28
Priority:Should have Due date:
Assigned To:- % Done:

0%

Category:Versioning and workspaces Spent time: -
Target version:-
TYPO3 Version:4.7 PHP Version:5.3

Description

If you move a child element inside a grid container in Draft Stage the element either gets moved outside the container, or it is lost on this page as it doesn't shop up anymore.

If it is not visible anymore in draft stage, it is display in live stage but only in backend. Frontend isn't affected.

If you push those changes to live stage, nothing happens. like any changes you have done are reverted.

Both cases appear randomly, i can't exactly find out why, but i think it has something to do if the moved element is not in colPos=0, or moved to colpos0

Example1: (attachment draft1,draft2, live1,live2).
You move an element and it gets displayed below the grid element. live stage shows correct position, if you publis it nothing happens.

draft1.png Draft Stage.
Move Record from bottom left to bottom right. (Record and gridcontainer+page are translated)
draft2.png
Element is moved outside grid container. (its impossible to move this element again inside the container regardless which column you choose)
live1.png
Live Stage shows moved element at correct position.
live2.png
After publishing those 2 changes (workspace says lang=0 and lang=1 element has been moved), both elements are unchanged. backend/frontend live/draft stage both display everything like it hasn't ever been moved.

Example2: (attachment draft21,draft22, live21,live22).
I don't know why but this happens only on one page with a grid-container. most of other pages i tested it works like example 1. Grid-Container is the same as on pages with example 1.

draft21.png Draft Stage.
Move Record from bottom left to top left. (Record and gridcontainer+page are translated)
draft21.png
Element disappeared in draft stage.
live21.png
Live Stage shows moved element at correct position.
live22.png
After publishing those 2 changes (workspace says lang=0 and lang=1 element has been moved), both elements are unchanged. backend/frontend live/draft stage both display everything like it hasn't ever been moved.

Thanks,
Maik Peuser

draft22.png - example2 draft2 (407.3 kB) Maik Peuser, 2013-03-28 14:35

live21.png - example2 live1 (30.8 kB) Maik Peuser, 2013-03-28 14:35

live22.png - example2 live2 (28.1 kB) Maik Peuser, 2013-03-28 14:35

draft1.png - example1 draft1 (28.3 kB) Maik Peuser, 2013-03-28 14:35

draft2.png - example1 draft2 (28.2 kB) Maik Peuser, 2013-03-28 14:35

live1.png - example1 live1 (23 kB) Maik Peuser, 2013-03-28 14:35

live2.png - example1 live2 (23 kB) Maik Peuser, 2013-03-28 14:35

draft21.png - example2 draft1 (29.3 kB) Maik Peuser, 2013-03-28 14:35


Related issues

related to Core - Task #29278: Lost relations on copying IRRE children in workspaces Rejected 2011-08-26
related to Core - Bug #38703: Publishing records with IRRE records -> lost relation Rejected 2012-07-06
related to Core - Bug #39317: Copying records with IRRE: subrecords only copied in Live... Closed 2012-07-27
related to Core - Task #45132: Faulty translation behavior of IRRE using workspaces Rejected 2013-02-04
related to Core - Task #45214: Problems on publishing complex IRRE structure On Hold 2013-02-06
related to Core - Task #45676: Workspace references are not considered Rejected 2013-02-20
related to Grid Elements - Bug #46952: Gridelements not working correctly with workspaces Closed 2013-04-05

History

#1 Updated by Maik Peuser over 2 years ago

Addition:
It behaves the same way if cut and paste elements instead of drag'n'drop them for both examples.

#2 Updated by Jo Hasenau over 2 years ago

  • Status changed from New to Rejected

Are you working on a default 4.7 core or did you install the pending patches related to IRRE and workspaces?

Grid Elements are based on IRRE and we already had several core bugs fixed by Oliver Hader, but the patches are still pending.
So without them you might still run into problems.

Please take a look at the list mentioned here http://www.startnext.de/typo3-grid-elements-2-0/pinnwand/ at the 6th of March and pick the ones matching your TYPO3 version.
And while you are on it, you could even do some reviewing so they will get the necessary votes to be finally merged.

If you are working with a patched core and still have the same problems, I will of course reopen this issue.

Also available in: Atom PDF