[Radiant] Conflicting updates

[Kevin Ansfield]

On 3/20/07, Jacob Burkhart <igotimac at gmail.com> wrote:
>
>
> Or, Maybe it's time to consider addding versioning and history tracking.
> If we detect a simulatneous edit, we simply save both versions.. one of
> those versions is the later version and one of them is the earlier
> version.  The User saving the later version would be notified of the
> conflict and be able to use the history and rollback functionality to
> resolve the conflict...



This is definitely something I've been considering as well, there's been
lots of cases where i've run into the need for version/history tracking,
usually with the outcome that I have to go back to a database backup from
the previous night for a client and get them to re-do a lot of work. I was
thinking of implementing something like the writeboard versions system that
is included in basecamp, although I haven't yet looked into how feasible
this is with the extensions system.

In any case, this approach certainly gets my vote! Especially if there is
also a notification when saving that modifications have been made since the
page/snippet/layout was opened.

Kev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.radiantcms.org/pipermail/radiant/attachments/20070320/40e54a8b/attachment.html