Allow unrevisioned node edits when $user can delete revisions

Created on 1 May 2010, about 15 years ago

Updated 8 March 2025, 2 months ago

If a node type's 'Create new revision' is enabled and the $user does NOT have 'administer nodes' permission, she cannot edit the nodes of this type without creating a new revision, regardless the fact that she is granted the 'delete revisions' permission. IMO if the $user is allowed to delete revisions, then she should even be allowed to edit the nodes without creating a new revision.

I was even thinking about taking the 'revert revisions' permission into account. If the $user is only allowed to revert revisions, but not delete them, then she is not allowed to hide her own edits from the history, so granting her the 'revert revisions' by itself should not allow her to edit a node without creating a new revision. OTOH if she is granted the 'delete revisions', but not the 'revert revisions' permission, then she can hide the fact that there was a revision before her own one, anyway.

In short, it is kind of usability improvement: allow the $user to edit a node without creating a new revision if she can hide the fact that there was any previous revisions before her own one (by deleting the old ones). The attached patch does this.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

node system

Created by

🇭🇺Hungary boobaa

Live updates comments and jobs are added and updated live.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 2 months ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024