Item2378: GROUPINFO needs a $allowschange format operator

Priority: CurrentState: AppliesTo: Component: WaitingFor:
Enhancement Closed Engine    
so that we can show/hide the add/remove UI as per the Group System's backend.

we can't just use topic permissions, because other mappers don't use topics..

similarly we need the same for the add new goup - presumably that would be a new format param on GROUPS

thus adding new api's to the mappers :/ (with the defaults being set to read only..)

set to feedback from the main mapper writers

unit tests needed: for allows change and for visibility / not based on ALLOWTOPICVIEW

$allowgroupview or similar might be needed to abstract the topic based permissions - none of the non-default mappers use the topic, and thus have a different way to manage who should see the group, or even the group members.

-- SvenDowideit - 18 Nov 2009

Sounds good. So this item also applies to all usermappers that are out there, i.e. LdapContrib

-- MichaelDaum - 19 Nov 2009

yes and no smile

So long as you inherit from Foswiki::UserMapping, you will get the default '$allowchange = 0' result.

my long term plan for HTTPDUserAdminContrib is to add cfg bit to limit viewing and changing groups - more inline with internet portals.

-- SvenDowideit - 20 Nov 2009

ItemTemplate edit

Summary GROUPINFO needs a $allowschange format operator
ReportedBy SvenDowideit
Codebase trunk
SVN Range SVN 5580: Foswiki-1.1.0-dev, Thu, 29 Oct 2009, build 5392
AppliesTo Engine
Component
Priority Enhancement
CurrentState Closed
WaitingFor
Checkins Foswikirev:5581 Foswikirev:5583
TargetRelease minor
ReleasedIn 1.1.0
Topic revision: r10 - 04 Oct 2010, KennethLavrsen
 
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. see CopyrightStatement. Creative Commons License