[
https://issues.apache.org/jira/browse/ROL-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed ROL-922.
--------------------------
Resolution: Won't Fix
I think the effort involved in trying to code locks accurately would not be
worth the benefit. Distributed teams need to communicate properly to avoid
overwrites from occurring.
> Editor lock for multiuser blogs.
> --------------------------------
>
> Key: ROL-922
> URL: https://issues.apache.org/jira/browse/ROL-922
> Project: Roller
> Issue Type: Improvement
> Components: Multi-Author
> Affects Versions: 2.0
> Reporter: Damien
> Assignee: Roller Unassigned
>
> The feature of a multi-author is nice but a problem that it creates is that
> if one author is currently editing a post that has been previously saved
> there is no way for another author who wishes to work on same entry to know
> it's being worked on. This causes overwrite of eachothers work. Last one
> saved will be the one that is kept.
>
> *If there was a checkout for editing feature this would solve the problem.
> A simple way to implement this would be locking the entry row when someone
> goes into edit mode on an entry. Only thing to really watch for is that
> there is an expiration time on the lock in case the editor exits without
> resaving the entry. Also a change to the edit entry comand so it realises an
> entry is locked and display a message to relay this fact.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
