Affected Version
2026.2
Affected capability
Data Objects, Documents, Assets
Description
Split out from the add-on request in #231.
Dragging an element onto another folder in the element tree performs the move immediately, with no confirmation. For a folder, that move rewrites the path of every element below it, so a single accidental drop can silently affect thousands of elements — @h3rrvorr4g3nd reports a folder with ~80k data objects being moved by accident, leaving invalid paths for everything inside it. There is no practical undo.
Note that #231 covers the most likely way to trigger this accidentally (selecting the tree pager's page number started a folder drag). That is a bug and is fixed separately; this request stands on its own, since a mis-aimed drop can happen without it.
Expected Behavior
A move triggered by drag and drop asks for confirmation when the dragged element is a folder, naming the source and the target path, and warns that all children get a new path. Moving a single element keeps working without a prompt, and reordering within the same parent does not change any path so it needs no prompt either.
Additional context
Deleting a folder already confirms this way (element.delete.folder.*), so the pattern and the wording style exist.
Open question for discussion: should non-folder moves confirm as well, or should the prompt be gated on the number of children? The proposal above deliberately keeps single-element drags friction-free.
Affected Version
2026.2
Affected capability
Data Objects, Documents, Assets
Description
Split out from the add-on request in #231.
Dragging an element onto another folder in the element tree performs the move immediately, with no confirmation. For a folder, that move rewrites the path of every element below it, so a single accidental drop can silently affect thousands of elements — @h3rrvorr4g3nd reports a folder with ~80k data objects being moved by accident, leaving invalid paths for everything inside it. There is no practical undo.
Note that #231 covers the most likely way to trigger this accidentally (selecting the tree pager's page number started a folder drag). That is a bug and is fixed separately; this request stands on its own, since a mis-aimed drop can happen without it.
Expected Behavior
A move triggered by drag and drop asks for confirmation when the dragged element is a folder, naming the source and the target path, and warns that all children get a new path. Moving a single element keeps working without a prompt, and reordering within the same parent does not change any path so it needs no prompt either.
Additional context
Deleting a folder already confirms this way (
element.delete.folder.*), so the pattern and the wording style exist.Open question for discussion: should non-folder moves confirm as well, or should the prompt be gated on the number of children? The proposal above deliberately keeps single-element drags friction-free.