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.
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.