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

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