Offer concurrent editing protection for all entities by including the changed timestamp to each entity form

Created on 1 November 2017, over 6 years ago
Updated 1 February 2023, over 1 year ago

Problem/Motivation

#2837022: Concurrently editing two translations of a node may result in data loss for non-translatable fields is dealing with properly detecting concurrent edits and it was noticed that currently the changed timestamp is put to the form only in the NodeForm, which allows for concurrent editing protection only for node entity forms that have been build through the NodeForm.

Proposed resolution

In order to cover all possible use cases the changed timestamp should be always part of the entity form and to achieve this we should add it in \Drupal\Core\Entity\Entity\EntityFormDisplay::buildForm() to the entity form, which will cover any entity form no matter how it is build, inline or not.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Needs work

Version

10.1

Component
Entity 

Last updated about 9 hours ago

Created by

🇩🇪Germany hchonov 🇪🇺🇩🇪🇧🇬

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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.

Production build 0.69.0 2024