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.
Deprecate the content_lock_timeout module and move all the functionality and configuration into content_lock
TBD
TBD
TBD
Active
3.0
Code
Issue #3530509 by alexpott: Merge content_lock_timeout into content_lock
Automatically closed - issue fixed for 2 weeks with no activity.