Problem/Motivation
Archived nodes linked to menu items, child menu links become orphaned, provide a useful report!
Example report:
→
Steps to reproduce
Publish a node titled "Example A" that has a menu link.
Publish a node titled "Example B" and other nodes that have a menu link which is a child of the menu link created for "Example A"
Now change the moderation state of the published "Example A" to "archived"
See the example report, get you an idea of what this is for.
Proposed resolution
New submodule called safedelete_menu_report.
Install this new submodule, then configure the options, the details for this is at the bottom of the /admin/config/development/safedelete
config form. I should probably move this form to /admin/config/content/safedelete instead or add a second link there but alas, need a new issue for that.
Remaining tasks
Publish a new release with the new submodule
User interface changes
See screenshot, new route /admin/safedelete-menu
and a new menu link underneith the "Content" part. A new permission is added, you'll want to configure this.
API changes
New submodule, requires a workflow such as "Editorial", requires configuration options to be configured.
Data model changes
New configuration settings.