Hi, just a quick UI thought --

I keep getting feedback that the number of OG administrative tabs are a bit overwhelming for group admins:
Faces | List | Add members | Configure member roles | Configure restricted member roles | Manage users

I keep wanting to see the 'Configure member roles' (and 'Configure restricted member roles') screens as Views, so they could be more... configurable :) -- We could then add them together, or separate them into different Views tabs as desired.

If the 'Configure member roles' admin screen could become a View, it could also be optional, and made available only if Views Bulk Operations is enabled. Derek Wright recently added a similar feature to the Signup module's administrative interfaces: #352328: Replace (optionally?) node/N/signups/admin with a views bulk operations view?. Out of the box, there is Signup admin form (for when Views and VBO are not enabled) -- but then, if Views/VBO are enabled, there's an option to replace that default form with a View, to allow these forms to be more configurable through the Views interface.

Any thoughts, or concerns with taking a similar approach to the OGUR group admin screens?

Comments

somebodysysop’s picture

somebodysysop commented
Status: Active » Postponed (maintainer needs more info)

Sounds like a terrific idea, but how difficult would it be to implement these forms as views? And, is there any clear documentation on how to use VBO to implement the business logic?

I'd be happy to look at a patch, otherwise it will take me a minute to come up to speed on something like this.

scottrigby’s picture

scottrigby
he/him
Primary language English
Location Brooklyn, NY
commented

I'm glad you like the idea - it would be great to see this implemented.

I was thinking if OGUR's 'Configure member roles' form could be added as a configurable action, VBO could be used out of the box to create a single 'Manage group members' view. A default View could be added as a list of OG users (like OG's og_members view @ og/users/%), with 'Views bulk operation' selected as the views style plugin instead of 'Table'. This would ideally narrow down the VBO selectable operations to whatever the managing user has permissions to operate. Something like these:
* Create Admin status on selected users (OG specific)
* Remove Admin status on selected users (OG specific)
* Approve membership request of selected users (OG specific)
* Deny membership request of selected users (OG specific)
* Unsubscribe the selected users (OG specific)
* Configure roles of selected users (OG specific)

This last action could lead to the confirmation / action configuration screen, offering the role options that the current managing user has permisions to configure (whether or not they have perms to configure only restricted roles, or configure all roles within the group). I haven't implemented anything like this myself, but I was thinking the link above to how this was achieved in Signup might provide some clues?

What do you think?

scottrigby’s picture

scottrigby
he/him
Primary language English
Location Brooklyn, NY
commented
Status: Postponed (maintainer needs more info) » Active

clip from VBO's project page:

A significant change from the D5/V1 version is that VBO can support all object types supported by Views. Natively, VBO comes with support for nodes, users and comments. Through the new VBO-defined hook_views_bulk_operations_object_info(), other modules can let VBO handle arbitrary object types. Refer to function views_bulk_operations_views_bulk_operations_object_info() (you'll have to search for it on the page sorry) for information.

May be a good place to start?

somebodysysop’s picture

somebodysysop commented

I'll take a look. Again, no idea as to how easy/difficult this might be. Anyone who has a clue please feel free to contribute.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Active » Closed (outdated)

I am closing this issue, as Drupal 6 is now not supported.