Bug #100504
open
processCmdmap_discardAction does not hand in DataHandler object (was: Deleting a container-element does not delete the childs of the container)
0%
Description
When I use the container-extension
https://extensions.typo3.org/extension/container
and create a container-element and then add some normal elements to it, everything is OK.
But when I am in a Workspaces-mode and then delete this container, only the container-element will be deleted.
The childs of the containter will not be deleted when I am in the workspaces-mode.
When I am in the live-workspace, every child of a container will be deleted too.
In the workspace-mode, the childs of a deleted container will be shown at the bottom of the page under the "Unused" column.
Because this happens only in the workspace-mode, this must be a bug in the workspaces-extension.
Updated by Georg Ringer about 1 year ago
- Status changed from New to Rejected
thanks for reporting the issue. I am closing this because I guess it is more related to ext:container.
I added your issue at the proper issue tracker https://github.com/b13/container/issues/387
Updated by Achim Fritz about 1 year ago
Hi @Kurt Gusbeth i cannot reproduce the bug, s. https://github.com/b13/container/issues/387#issuecomment-1509878228 , can you help?
Updated by Benni Mack 11 months ago
- Subject changed from Deleting a container-element does not delete the childs of the container to processCmdmap_discardAction does not hand in DataHandler object (was: Deleting a container-element does not delete the childs of the container)
- Status changed from Rejected to Accepted
I think we should keep this one open, as the processCmdmap_discardAction() does not hand in the DataHandler instance currently, which should be adapted in Core.