Answers.Body: <p>There currently isn't a native way to do this and I'm not aware of a plugin that's has the functionality.</p>
  
  <p>You can semi-work around it with entry revisions, but if you think this should be a core feature you can <a href="http://feedback.craftcms.com/forums/285221-feature-requests/suggestions/9009169-add-an-alert-or-warning-when-multiple-authors-are" rel="nofollow">vote for it</a>!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-22T09:53:48.543Z
Answers.Text: Looks like I might have to make this plugin maybe
Answers.UserDisplayName: Anthony Cossins
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-20T17:18:45.403Z
Answers.LastActivityDate: 2016-06-20T17:18:45.403Z
Answers.UserDisplayName: Brad Bell
Body: <p>If 2 or more people are editing a entry at the same time in Craft, the last person to save the entry overrides everyone else's work. It doesn't seem any diffing is involved to resolve this. I'm using matrix fields mostly.</p>
  
  <p>WordPress handles it by locking a post while someone is editing. This is done by sending an AJAX request to the server when auto saving, updating the "last edited" date and which user is editing.</p>
  
  <p>Does anyone know if a plugin exists already for Craft that implements this post locking feature? Or is there something already in Craft to avoid these conflicts?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-06-20T14:25:10.270Z
Comments.Text: You can workaround the problem with entry revisions. If you want to see it added, [vote](http://feedback.craftcms.com/forums/285221-feature-requests/suggestions/9009169-add-an-alert-or-warning-when-multiple-authors-are) for it.
Comments.UserDisplayName: RitterKnight
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-06-20T16:17:04.427Z
Comments.Text: @RitterKnight Voted! Revisions is useful to get back lost work but still a pain because you can't rollback specific parts
Comments.UserDisplayName: Anthony Cossins
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-06-20T17:07:34.053Z
Comments.Text: I agree. Would be nice to see feature parity in this respect with WordPress.
Comments.UserDisplayName: RitterKnight
Tags: <entries><users><admin><saveentry><editor>
Title: How to handle multiple users simultaneously editing an entry?
ThreadText: # How to handle multiple users simultaneously editing an entry?
  
  (Asked by: username_0 on 2016-06-20)
  
  If 2 or more people are editing a entry at the same time in Craft, the last person to save the entry overrides everyone else's work. It doesn't seem any diffing is involved to resolve this. I'm using matrix fields mostly.
  
  WordPress handles it by locking a post while someone is editing. This is done by sending an AJAX request to the server when auto saving, updating the "last edited" date and which user is editing.
  
  Does anyone know if a plugin exists already for Craft that implements this post locking feature? Or is there something already in Craft to avoid these conflicts?
  
  **Tags:** entries, users, admin, saveentry, editor
  
  > **Comments:**
  > **username_1**: You can workaround the problem with entry revisions. If you want to see it added, [vote](http://feedback.craftcms.com/forums/285221-feature-requests/suggestions/9009169-add-an-alert-or-warning-when-multiple-authors-are) for it.  
  > **username_0**: @username_1 Voted! Revisions is useful to get back lost work but still a pain because you can't rollback specific parts  
  > **username_1**: I agree. Would be nice to see feature parity in this respect with WordPress.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2016-06-20. Score: 1 | Accepted answer
  
  There currently isn't a native way to do this and I'm not aware of a plugin that's has the functionality.
  
  You can semi-work around it with entry revisions, but if you think this should be a core feature you can [vote for it](http://feedback.craftcms.com/forums/285221-feature-requests/suggestions/9009169-add-an-alert-or-warning-when-multiple-authors-are)!
  
  > **Comments:**
  > **username_0**: Looks like I might have to make this plugin maybe  
  
  ---
  
  