Better handling of editing conflicts

Created on 5 January 2007, over 18 years ago
Updated 18 July 2025, 1 day ago

Currently, the locking function of Drupal handles editing conflicts in a very heavy-handed way: "This content has been modified by another user, changes cannot be saved."

A future version could take a leaf out of the book of MediaWiki, which handles this much more smoothly: The current version of the article is shown above, the still unsaved conflicting edit in another text box below. This allows the user to easily paste the section they edited into the above text, merging the two versions by hand.

In contrast, having to copy the section, reload the page and resubmit is less convenient than it could be.

✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

entity system

Created by

πŸ‡¨πŸ‡­Switzerland cburschka

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

  • stale-issue-cleanup

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

Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. 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!

Production build 0.71.5 2024