Grid Elements

Actually the list view is still problematic, which is why we provided a page TSconfig switch to disable child elements in the list view. So that you can not break relations by moving elements up and down the list.

TCEFORM.tt_content.tx_gridelements_backend_layout.removeChildrenFromList = 1

Another workaround is to move elements using the page module instead, since you will have the option to paste them into the desired page or content columns. With grid elements installed this will even work with empty columns, so there is no need to use the list module as a workaround anymore.

We are currently working on proper solutions for the list module problems though, so we appreciate your feedback.

Could you please provide more details? - What is the exact chain of actions you have taken? What are the results after each step?

If the element is really moved from one page to another, it should be just impossible that it will "remain" on both pages, since even grid elements have got a "pid" field having a unique ID of the parent page. So IF the list module shows the element twice on different pages, there MUST be at least two different elements.

I was able to reproduce the problem adn uploaded a fix to current trunk.

It's been the pidSelect setting used by grid containers to determine the id to take their children from. The core comment says, it has to be a list of IDs, but actually it expects a whole query part here. So it's not enough to just set it to a pid. It must be something like

pid = 1

or

pid IN (1,2,3)

instead. After fixing this, the grid containers just get elements from the current page.

This still does not fix the rest of the problems with the list module, but at least it will remove "virtual double elements"