Item11923: Changes to AdminGroup by the group API should always force a new revision.

Priority: Urgent
Current State: Closed
Released In: 1.1.6
Target Release: patch
Applies To: Extension
Component: TopicUserMappingContrib
Branches: Release01x01 trunk
Reported By: GeorgeClark
Waiting For:
Last Change By: GeorgeClark
In most cases it's probably find that multiple changes to a group topic are accumulated into a single topic revision per the {ReplaceIfEditedAgainWithin} setting (default 3600 seconds). However the admin group is important enough that every change should be separately recorded.

Detect if AdminGroup is being modified and set the forcenewrevision flag on save.

Also some better logging is needed.

-- GeorgeClark - 03 Jun 2012

Only downside of tracking every change ... Can't see group membership aka settings from prior revisions, unless you use raw=debug. Settings are always read from the current rev.

-- GeorgeClark - 03 Jun 2012

ItemTemplate edit

Summary Changes to AdminGroup by the group API should always force a new revision.
ReportedBy GeorgeClark
Codebase 1.1.5, trunk
SVN Range
AppliesTo Extension
Component TopicUserMappingContrib
Priority Urgent
CurrentState Closed
Checkins distro:0dd89549a795 distro:f6498a76bb53
TargetRelease patch
ReleasedIn 1.1.6
CheckinsOnBranches Release01x01 trunk
trunkCheckins distro:f6498a76bb53
Release01x01Checkins distro:0dd89549a795
Topic revision: r5 - 02 Dec 2012, GeorgeClark - This page was cached on 25 Oct 2016 - 19:24.

The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License