Better markup of changed and deleted content

Created on 10 March 2015, about 10 years ago
Updated 8 May 2025, 2 days ago

Problem/Motivation

We had the problem that editors of our customers didn't really see if content was changed and within this content some strings were also removed. This was just displayed as diff-changed. So timetimes they did not really realized whcih sting was now changed and whoch was removed. this is a little patch to improve this display behaviour a little bit.

For example: the text "For almost 90 years ..." was changed into "For 90 years ...". The diff module displayed this as diff-changed and the editors did not really have seen that the almost was removed.

Proposed resolution

This patch changes the display behaviour in class _DiffEngine function diff() a little bit and also displays the removed content before showing the changed stuff. So it is visible which content was removed.

Remaining tasks

this is just a little patch, just tested in our environment. Still needs to be verified to work with other Drupal environments.

  • needs review
  • needs testing

User interface changes

Changes in the user interface. If there were previously changes in the text containing changed text and also deleted strings, just the changed text was displayed wrapped with a . Now first there will the deleted text displayed with a and then the changed text will be displayed with the

API changes

no API changes

Feature request
Status

Postponed: needs info

Version

11.0 🔥

Component

base system

Created by

🇩🇪Germany Carsten Müller

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

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