Merge content_lock_timeout into content_lock

Created on 17 June 2025, 18 days ago

Problem/Motivation

For many years people have wanted the ability to release a lock when you navigate away from a content edit screen but with issues like πŸ› Previewing appears to unlock node RTBC this is going to be extremely complex to offer.

After a long discussion with @chr.fritsch and @daniel.bosen we've decided to make functionality provided by content_lock_timeout part of the default experience. This will make it less likely that content is locked when a user edits a node and we can also check the timeout when determining with content is locked.

Proposed resolution

Deprecate the content_lock_timeout module and move all the functionality and configuration into content_lock

Remaining tasks

User interface changes

TBD

API changes

TBD

Data model changes

TBD

πŸ“Œ Task
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024