Add ability for group manager to close a group [#70494]

I am going to build a intranet site using drupal with organic groups.
I need to have many different groups (almost hundreds) inspite of few members (less then a hundred).

The problem is that with so many groups a member posting content will face a very big form to choose groups.
So I think to let group admin close old groups: members will have view permission but they couldnt post or modify content on closed groups.
A closed group will not appear in the audience form and in the user profile, reducing dimension of that pages.

I don't know og code very well, and it's a big module to try a patch by myself without help from clever people.

I think that could be an intersting feature for anybody using this module.

Comments

Comment #1

moshe weitzman CreditAttribution: moshe weitzman commented 26 June 2006 at 01:45

ok, so i would call this group status 'closed for posting' or 'archive' mode. some other decisions to be made such as, do these groups show up in the directory ... anyone else interested in this? i'm not going to work on it myself but i'd review such a patch. also needs proff of demand for the feature.

Comment #2

webchick

she/they

English

Vancouver 🇨🇦

CreditAttribution: webchick commented 26 June 2006 at 02:09

I'll +1 the feature request, though most likely won't be implementing it myself either. For example, on groups.drupal.org, it would make sense to archive groups that were there around event planning and such so they're still available for historic purposes but people aren't posting there anymore. Right now this is done with taxonomy + views but a more "integrated" archive feature might not be a bad idea.

As far as browsing goes, I guess maybe make a separate tab for them on ?q=og if they exist.

Comment #3

leoburd CreditAttribution: leoburd commented 5 July 2006 at 18:26

- I also think it would be great if groups could be archived.

The way I see it, users/group admins should have the option to browse archived groups, reactivate archived groups, and even flush the contents of groups that are not going to be used anymore. Would that make sense?

In terms of implementation, how should those functions be done? Should they be incorporated into og.module or should they be placed in a separate module? How difficult do you guys think it would be to implement the functionality proposed?

Thanks in advance,

Leo