About Organic Groups Mandatory Group

My point about recipes; how to use and configure specific modules to accomplish added functionality; was that some interesting functionality might not be useful to all Commons based sites. The benefits are that functionality that is less mainstream would be more available to those who want it. Also it could be available now, or whenever, and not be dependent on a Commons release. Anyone can contribute a "how to" recipe for additional Drupal modules. Also, hopefully Aquia will offer some things they might do for a specific website that they might decide is not suitable for the "core Commons".

What also might be helpful in the long run are recipes for specific genres of sites.  In other words, lists of modules that can help someone create the ultimate site they are looking for.  For example, we are utilizing DC to create a small community social networking site (connecting people in our metro area who play all forms of "unplugged games" .. board games, card games, RPGs, etc.)   So, the functionality that originated this thread would actually be extremely useful to us.  Here's a specific example:

We have a need to create recurring events that people can RSVP to.  (We also need those recurring events to appear as individual nodes so that they can each instance of the event can have it's details adjusted/modified when needed, but that's another challenge altogether).  While individual groups will create the majority of events, there will be some events where any member of the community should be invited to attend.  The problem is that the RSVP module does not offer the ability to "invite all users".  You can either invite all users of a Group or invite individual users.  Our current "work around" is that we've created one "main public group" and will work to make everyone aware that they need to join it if they want to be made aware of and RSVP to public events.   We'll make this easy by having it be a group they can join at registration.

What would be ideal is for everyone who creates an account to be automatically joined to this group.  As others have pointed out, this is not likely a feature that should be part of the "core" of Commons since it's utility is not as universal as something like recurring events (hint, hint).

Back to the recipe piece.  If there is interest, I'm certainly willing to share our final "recipe" for our site as an example of a "community networking" recipe once we've gotten everything established.

Ideally, I would like to have a way to have part of a DC site viewable to the public and part viewable to one private group. Ideally, there might be sub-groups under the private group, particularly if that is the way to keep things private.

So, until I know what this might look like and and when it might be available, I expect to roll out with just one private group that all discussions will take place in. Then, if I get lucky, tags will provide a way to move discussions into appropriate sub-groups down the road.

With only one group available, and if understand correctly a limitation of what users can do without joining that group, it would be easier for them to be joined automatically in that group, once their membership is approved.

I could see it making less sense when there isn't any single group everyone should be part of, but if everything is group-centric, I think it makes sense to have a default group.

In the meantime, can we assume that adding the module is safe and won't break anything in a future revision? Also, if I use it can I use drush to download and enable it?

Thanks.

What do you think about Organic Groups Mandatory Group module to be considered for Drupal_Commons

It's a must for any DC-admin, otherwise broadcasting became big headache

I really like your way of expressing the opinions and sharing the information. It is good to move as chance bring new things in life, paves the way for advancement, etc.
350-030 braindumps ///