Broken drag and drop in V12

[MajPay]

A customer just issued a bug: When they move a content element to a certain position, it will always be moved to the very end. Sounds strange but can be reproduced.

If you drag a regular content element beneath a container element and reload the backend, the element is at the end of that colPos. Happens only in the translated version of that page.

Might be related to #690

You recently dropped support for V12, but that bug was introduced with some update, where it was still supported. And this might happen in V13+ as well, did not check. Can someone tell us what lower version of ext:container can safely be used instead? Downgrading to 3.1 and waiting for the V13 Upgrade of the project would be fine for us but if it leads to corrupted states, it's a no-go.

Update: I initially added a clue about the javascript overrides, but removing the hooks works as well.

[MajPay]

If i disable the CommandMapBeforeStartHook, it works as expected.

I highly suspect this commit:
3606463

But i don't have time to dig further.

[achimfritz]

Hi @MajPay , did you check the container:sorting? (and container:sorting-page-command)?

[MajPay]

No but i just did - it had no effect. In my case, the content element, that is being dragged is not a container-element, but the "target" content-element. The "target" content-element is the content-element, after which you drop the dragged element. In that case, after reloading the backend, the content-element will not rendered where you dropped it, but at the very end of the colPos. And it only happens in page-translations, not in the default language.

[MajPay]

@achimfritz From what i have seen in the git history, you have been involved quiet a lot in the whole sorting topic (excuse me if i am wrong on this). Can you tell me if you have the time or when you might have time to investigate this? I need to update our customer on this issue. Let me know if some additional information would help. Best regards

[achimfritz]

Hi @MajPay , i can not see the behaviour on our installations or on a vanilla installation, please give me a detail description how i can reproduce this behaviour, with an vanilla-installation (core + EXT:container + EXT:container-example).

provide a db dump of tt_content before your actions
describe exactly what you do
provide a db dump after your actions

would be perfect.