Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
content lock issue - if a node is locked for editing by other user, the node can still be edited by a different user using the quick edit
Comment | File | Size | Author |
---|---|---|---|
#7 | content_locking_d7_edit.png | 55.95 KB | Wim Leers |
Comments
Comment #1
webchickMoving to the Edit queue. (Which is not easy these days, heh. #2164711: Moving an issue's project to a short, common project name requires dark magicks)
Comment #2
Wim LeersGábor worked on fixing this in Drupal 8. Assigning to him for guidance.
(In short: Drupal 7 uses a hack to do locking, there's no API for this. So Edit will have to use the same hack to be compatible with it, probably.)
Comment #3
Gábor HojtsyI think Edit will need to use the same timestamp checking to do this. Drupal 8 does the same timestamp checking, it is just more encapsulated, less of an evident hack really. Drupal 7 only has this feature for nodes, so Edit only needs to implement for nodes too. A little one-off thing. I don't know better unfortunately.
Comment #4
Gábor HojtsyComment #5
Wim LeersI will use #1901100-86: Make Edit module work with TempStore, so revisions are not saved on all atomic field edits as an example.
Comment #6
Wim LeersDone!
http://drupalcode.org/project/edit.git/commit/c644d8e
Comment #7
Wim LeersI forgot to upload the accompanying screenshot: