Return-Path: X-Original-To: apmail-roller-commits-archive@www.apache.org Delivered-To: apmail-roller-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6E0EF10BDB for ; Sat, 24 Aug 2013 02:43:57 +0000 (UTC) Received: (qmail 31756 invoked by uid 500); 24 Aug 2013 02:43:56 -0000 Delivered-To: apmail-roller-commits-archive@roller.apache.org Received: (qmail 31454 invoked by uid 500); 24 Aug 2013 02:43:55 -0000 Mailing-List: contact commits-help@roller.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@roller.apache.org Delivered-To: mailing list commits@roller.apache.org Received: (qmail 30442 invoked by uid 99); 24 Aug 2013 02:43:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 Aug 2013 02:43:52 +0000 Date: Sat, 24 Aug 2013 02:43:52 +0000 (UTC) From: "Glen Mazza (JIRA)" To: commits@roller.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (ROL-922) Editor lock for multiuser blogs. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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