Problem/Motivation
In #2858431: Book storage and UI is not revision aware, changes to drafts leak into live site and related issues we've added entity validators to prevent draft revision changes modifying book outlines, menu links or path alases, all of which aren't versioned.
However, rather than requiring you to change this from the node form only when you publish a draft, it's also possible to make changes directly vs. the respective admin UIs for those subsystems.
So in the validation message, we could add a link to those UIs - if something happens to have a draft edit, but you wanted to move it in the book outline independently of that (and used the node form as a contextual way to do this), signposting to the admin UI might unstick you.
Comments
Comment #6
Sam152 CreditAttribution: Sam152 as a volunteer and at PreviousNext commentedI believe this belongs in the book component, given that's where the validators are.
Comment #15
quietone CreditAttribution: quietone at PreviousNext commentedThis extension is being deprecated, see #3376070: [Meta] Tasks to deprecate Book module. It will be removed from core and moved to a contrib project, #3376101: [11.x] [Meta] Tasks to remove Book.
This is now Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
This issue may be re-opened if it can be considered critical, If unsure, re-open the issue and ask in a comment.