I would second the notion. Let me add my rationale:

• Together with djangocms-versioning pages can never be deleted unless they do not have a single page content object or a setting is changed.
• The impact of deleting a page is more transparent in the page tree: All languages and all child pages are affected. (I know all elements are shown in the confirmation dialogue - but that typically is extremely long and hard to grasp.) This is the asymmetry to the "New Page" menu entry.
• It should not depend on the edit mode or publication status of the PageContent.

The alternative would be:

• Only show the delete menu entry if deleting is actually possible in the setup (might be complex in relation with versioning)
• Allow deleting in all edit models: preview, edit and "view on site".
• Only grey out if the user lacks permissions

In the course of this, I would also remove the item "Duplicate this page".

Reason is, that users have no way to specify the target and hence that duplicate would end up as a sibling of the target with a slug named "copy-of-…". By allowing the create duplicates from the page tree, this problem can be avoided because normally those duplicated pages are added to a different parent anyway.

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions.