Description of the need
Sometimes when revisions are on by default, no log message is added and you can end up with a lot of revisions with no log message. Then in retrospect, you might find some revisions are referenced more frequently than others, like a page relaunch. It would be nice if an author/editor could update the revision message to make it so they can track that revision more easily.
Proposed solution
Under the node/[nid]/revisions tab, add an operation for "Edit message" or "Edit log" that takes you to node/[nid]/revisions/[vid]/edit-message, that just displays a single textarea for adding/editing a log message.
Alternatives that have been considered
Long-term switching this to a modal would make sense, but we'd need the form and stand-alone page as a non-JS option anyway.
Additional information
GitHub Issue #:
5861
Recent comments
The user fills a form on an Application node, that then flicks off emails, and responds with a Thanks page. Nothing too complex. Just that the deletion of the page providing the expected...
Problem upon submission
Please can you say more about the Rule? What does it do? Does it use any other Rule supporting modules? I presume if you disable the rule and create/save the node then you don't get the...
Problem upon submission
Yeah, so never mind. The issue arose because a page was deleted that had the URL-alias that the Rule was trying to redirect to. Maybe Core could have caught that the URL didn't exist, or...
Problem upon submission