Bug #82291
open
Pasting of already deleted records should not be possible
0%
Description
In the case where you have multiple people working on content or multiple tabs open, it's possible to paste a CE that was already deleted.
This can leads to problems in extensions that do not expect to be called by the "processCmdmap_postProcess" hook.
For example, this leads to an issue with Flux where the "sorting" of copied content get's messed up.
Updated by Filipe DA COSTA COSTA over 6 years ago
An example of a possible problem can be found here : https://github.com/FluidTYPO3/flux/issues/1457
Updated by Oliver Hader about 6 years ago
- Status changed from New to Needs Feedback
Can you please provide the required steps in order to reproduce this behavior?
Or is it about the copy command to checking whether a record has been deleted? If so, this should be reproducible in a new functional test case...
Updated by Filipe DA COSTA COSTA about 6 years ago
Oliver Hader wrote:
Can you please provide the required steps in order to reproduce this behavior?
Or is it about thecopycommand to checking whether a record has been deleted? If so, this should be reproducible in a new functional test case...
Yes, it's about he copy command. It get's executed without checking if the record is deleted.
How you can reproduce the "processCmdmap_postProcess" on a deleted record:
- Open a first Tab A and copy a CE
- Open a second Tab B. The "Paste" button should be present
- In Tab A remove de CE
- Return to Tab B and "paste" the CE by pressing the button
DataHandler:process_cmdmap is called and a "copy" command is executed.
After this, the "processCmdmap_postProcess" hook is triggered but with an empty "$this->copyMappingArray" what caused the problem in flux.
As of today, this issue was fixed in flux, but the maintainer asked me to open a ticket anyway as he thinks that the hook should not be called in the first place.
Updated by Riccardo De Contardi almost 6 years ago
- Status changed from Needs Feedback to New