Issue Bug Closed

#108005Moving an element creates an unwanted copy.

Martin Pribyl 11/07/25, 10:45 updated 02/04/26, 20:24

Description

After copying & pasting a content element (CE) on a page, then a move of another CE (over drag&drop) causes the previously pasted CE to be pasted again after the page autoreload.

Steps to reproduce

Go to Backend → Page module and open a page with several CEs.

In the context menu of a CE, choose Copy.

Paste the CE somewhere on the same page (e.g., “Paste after” below another CE).
→ The pasted CE appears as expected.

Without leaving/reloading the page, drag a different CE to a new position.

The Page module reloads to reflect the new order.

Reviews 2

Files 1

History 48

  1. Martin Pribyl commented and changed attached Screen Recording 2025-11-07 at 12.24.38.mov <span data-processor="relativetime" data-value="2025-11-07T11:25:30+00:00" > 11/07/25, 11:25 </span>

    I’m not sure about the mentioned issue, but I think it’s not the same. My issue is pretty simple to understand what’s happening.

    1) you paste an element
    2) you try to move any of the element on the page over drag and drop (no issue with the base behaviour)
    3) then the page autoreload (to show correct new order), but the autoreload triggers the last request (post request of inserting the element from step 1, also with the original order).

    the behaviour of 3) is like if you try to reload the frame right after step 1)

  2. Riccardo De Contardi commented <span data-processor="relativetime" data-value="2025-11-07T13:57:10+00:00" > 11/07/25, 13:57 </span>

    IMHO it is the same issue as https://forge.typo3.org/issues/107970 – the element copied is the one you are dragging and dropping

    - you can experience it even without the initial copy & paste
    - you see a green “+” icon when dragging and dropping the CE

  3. Georg Ringer commented and changed status Under Review Closed <span data-processor="relativetime" data-value="2026-02-04T20:24:10+00:00" > 02/04/26, 20:24 </span>

    I am closing the issue as this has been fixed in chrome. hope this is ok for you, otherwise feel free to contact me via slack