Editorial content is not deleted immediately. It is first marked for deletion. The deletion happens when the change is published. This provides an opportunity to restore content deleted in error. If workflow is enabled the deletion may be delayed until approved.
Note that when content is deleted it is permanently removed from both instances and cannot be restored.
To delete content:
- Select the item and click Delete.
- Confirm the deletion in the dialog.
- The item is marked for deletion and the trash can icon renders next to the name. At this point in time:
- A version is created.
- You can still restore the item.
- Click Publish deletion to complete the deletion process.
- If workflow is enabled the item is sent to a publisher for approval.
- If workflow is not enabled, the item is removed from the tree.
Deleting multiple items
You can delete multiple items simultaneously by checking them and executing the Delete action once.
In the Enterprise Edition the confirmatory dialog includes a list of of dependent pages to warn editors of unforeseen consequences of the deletion. This functionality is provided by the Content Dependencies module. Dependent pages include child pages and pages that are linked through internal teaser components.
The Restore previous version action restores an item to the state it had before deletion. You can only restore items that are marked for deletion. Once the deletion has been published you can no longer restore the item.
In the Pages app, the restore action restores the whole subtree (recursive). This allows you to recover quickly if you delete a page and its children by accident. Recursive deletion is configured by default only in the Pages app. Other apps restore only the selected item. Magnolia 5.3.4+
To use reuse the recursive restore action in your app, set the definition
You can use all common action properties and the following:
parentNodeTypeOnly: Optional. When
false, the action restores all descendants of a parent node whose type is in the
mgnlnamespace. This is the most common use case. For example, in the Assets app you would want to restore a folder and the assets it contained. When
true, the action restores all descendants whose node type is the same as the parent node's. This is used in the Pages app where the action restores only pages, not their areas and components. Default is