[buddypress-trac] [BuddyPress Trac] #7210: Group type frontend integration

[buddypress-trac]

#7210: Group type frontend integration
-------------------------+--------------------
 Reporter:  r-a-y        |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  2.7
Component:  Groups       |     Version:  2.6.0
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |
-------------------------+--------------------

Comment (by hnla):

 Allowing for a value to be set to represent a default checked=checked  on
 register is a good idea, let the dev or admin decide which 'type'
 represents a 'normal' or 'default' group for their install.

 Of a lesser note are we concerned that in an existing install of groups if
 one then sets a new group 'type' then creates or associates a group to
 that type we now have a group list with a column that shows a group type
 string(label) for perhaps one group but the rest of the type columns for
 groups are empty, likewise create steps shows one group type, the
 possibility of creating a non group type exists but isn't clear?

 My feeling is that we do:

 Types are registered with `bp_groups_register_group_type` this action
 prompts BP to assume a type 'Normal' (terminology is wrong but...)

 BP sets a type 'normal' for all groups unless create steps or admin
 backend has overridden with a new or specific type from the choices (yes
 this step is problematic as it means running through all groups adding
 values to the type field so perhaps not a great idea).


 A new param is provided to allow for a preset checked=checked to exist for
 a chosen type.

 If this param wasn't set and if BP did set a type 'Normal' the default
 selection would be this value 'normal' set by BP automagically.

 A new param is provided that allows for a descriptive string to be set on
 create steps for the type checkbox items:
 `'create_step_types_descrip' => 'Please select the group type from the
 available options or leave as the default selection set',`

 That last option is really not massively important but could be nice but
 how that is generated to screen needs thought so that appropriate markup
 would be generated so likely a step too much at this stage.

--
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/7210#comment:20>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac