Organic Groups (OG)

Provides a field that can be used to indicate which other groups membership should be "promoted" to be a member of this group. Works similarly to og_promote, except for groups.

One word of warning, if you were to change the list of promoted groups, then the members of the old groups would remain..

There's an up-date all button in the admin section, it promotes everybody who is entitled to be promoted.

Allows organic groups to have its own file repository, control the access so only members from that group can upload/download the files.

Sponsored by Krimson and IBBT.

Default Roles allows multiple roles to be granted (and/or revoked) by each group. This is useful if you wish to use membership in certain groups to grant site-wide roles/permissions. For instance, you could have an "Editors" group, whose members will be automatically granted several appropriate roles at the time they join the "Editors" group.

This module allows for integration between Comment and Organic Groups so that only group members can comment on group content. Flexibility is greatly expanded in the new Drupal 7 version.

As always, feedback and patches are welcomed!

Compatibility with OG 7.x-2.x would be released shortly.
And Drupal8 compatibility would be ported as soon as OG has a Drupal8 version. (https://www.drupal.org/node/2718275)

OG Collections has been deprecated in favor of OG Blueprints. The ONLY reason you should download packages from this page is if you're a former OG Collections user, and you need to migrate your data over to OG Blueprints. The scripts for migrating your data are the sole changes in the 5.x-1.0-terminal release.

Screencast

• Demo showing how much time you can save creating structured nodes with this module
• Demo of the keyboard shortcuts functionality provided via jwerty integration

The Outline Designer is a user experience module that makes book management more intuitive.

Tutorial of Alpha 4 in action

Easily create subdomains per user, taxonomy term, content type, or organic group. This module adds an easy text field to the entity where you can enter a subdomain for it.

• User: e.g. "Mary" and all of her content at http://mary.example.com
• Taxonomy: e.g. "Seattle" and all content tagged with it at http://seattle.example.com
• Organic Group: e.g. "MyGroup" and all of its content at http://mygroup.example.com
• Content type: e.g. "News" content type and all of its nodes at http://news.example.com

Formerly part of the Devel module package, Devel Node Access (DNA) displays information related to the node access mechanism of your Drupal installation.

The {node_access} table and functionality are part of Drupal core, but they lie dormant until you install one or more node access modules that supply entries into the {node_access} table. Each node access module provides different strategies for controlling what each user can do with your nodes.

DNA has three audiences:

• It helps Drupal admins understand what is happening on their site, visualize how node access modules interact, verify that their customizations give the intended results, and finally answer the famous question: Why does this user have access to that node?
• It helps module and website support diagnose issues with node access on remote sites by instructing their clients to post screenshots and/or cut&paste listings of DNA output.
• It helps node access module developers implement and test proper behavior of their modules.

DNA is a tool for module and site development; it is not intended to run continuously on production sites, and its output is of no interest to website visitors, but if you run any node access module, DNA will help you with your work.

OG Blueprints will never be _directly_ ported to D6 - when the time is right, it will be rewritten as a core part of CTools/Panels.