Organic Groups: Enable users to create collaborative groups
Organic groups enables users with permissions to create and manage their own groups. Community members often want to self organize or spontaneously organize around a topic of interest. Allowing communities to organize naturally is important part of a healthy community.
An organic group is created by a single group owner, who has special permissions including the ability to delete the group the owner created. Group admistrators also have special permissions but can not delete the group unless they are assigned to be the group owner. Group subscribers communicate amongst themselves using the group home page as a focal point. They do so by posting the usual content types: blog, story, page, etc. A block is shown on the group home page that links to these group specific posts and actions. The block also provides summary information about the group.
Groups may be selective or not. Selective groups require approval by the group administrator in order to become a member. Organic groups also support private groups which will not be displayed in a list of organic groups. You cannot use this module with other node access modules.
You can:
- enable organic group creation and administration permissions at administer >> access.
- create organic groups at create content >> group.
- view a list of organic groups at groups.
- administer organic group at administer >> settings >> og.
- disable commenting and attachments for nodes of type group at administer >> content >> configure >> content types >> group.
- enable group details block, group subscriber block, new groups block, and my groups block at administer >> block.
- subscribe to groups by selecting the subscribe link in the group block.
- create content, invite friends, manage subscriptions, view list of subscribers, and see the group administrator in the group block.
- enable images in the group details block if you have the image module installed.
- file issues, read about known bugs, and download the latest version on the Organic Groups project page.
Setup under 5.0
Now you can go to Create Content>>Group and create your first group.
Updated 1/27/07: to reflect 5.0 installation of contrib modules into /sites/all/modules instead of /modules
Correction to step 4
Type = groups (must be lowercase).
Thanks for the step-by-step. Seems to work well.
If upgrading from 4.7
To upgrade from 4.7, I had to name the type 'og' instead of 'groups.'
Access Control
Right after step 5 and before creating content, you also need to go to Admin>>User Management>>Access Control and set certain roles to create and edit and edit own Groups.
______________________
Grand Junction Design, LLC
Web and Print Design For
Nonprofits and Foundations
Maybe This step by step will help you.
Maybe This step by step will help you.
Setting up Organic groups configuration
* go to module configuration
* go to Organic groups configuration
* go to "Group home page" and expand
* there will be a list of "Group home page node types:" you will need to add a "group" node type
* click the link that states "create a simple node type" at the bottom of the page
* click the link that states "Add content type"
* fill in fields make "type" called "group"
* return to "Organic groups configuration" page in module configuration expand "Group home page"
* you should now see a "group" field for selection highlight it and save configuration
Setting up URL alias configuration for groups
* go to module configuration
* go to URL aliases
* click "add alias" link
* Existing system path: = node/add/group and og/add
* click "update alias" button
Organic groups access control
* go to administration
* go to "Organic groups configuration"
* pull down "Access control"
* click "Enable" button to enable access control for post to controlled groups
a bit confused...
I am a bit confused with this, right now if I navigate to node/add/group I am taken to the correct location, the correct add group page of the content type group that I created. If I navigate to og/add I am taken to the add view page. These are two different locations, am I misunderstanding something? Won't you loose access to the node/add/group if you alias it to the og/add which would then bring you to the views page when navigating to /node/add/group??
I think...
...that this is referring to "these are the existing aliases for OG, alias them to what you want", not alias one onto the other :)
Kineta Systems - Web Development in Nottingham