This project is not covered by Drupal’s security advisory policy.
Nutshell:
This module allows for using taxonomy terms as a group. Kind of like the groups module but a more simplified version, for users and content.
Long winded version:
Since we have the taxonomy term entity we can use them as more then just categories we can use them as user groups!
If we have a reference on a user to a taxonomy term then in-fact that is a user group.
If we have a reference to a term on a content then that is group of content
if they are the same reference then that content belongs to that user group
this module provides the configuration and “permissions” (ad hock permissions)
to make the above work smoothly .
What this module is not:
This is not a replacement for the group module but just a different way to implement user / content grouping with out the need for reference entities. (as the term is already the reference)
What this module does:
- This module handles configuration,
- adhoc permissions,
- group membership approval (via block)
- allow for group admin users to edit their related taxonomy terms
- allow for group admin / members to manage group content based on simple config
- auto tags content with user field value on node create (so you can hide the reference field in form mode)
- offers hooks to make your life easier.
What this module does not do:
- set up a vocabulary to use
- set up roles to use
- set taxonomy term reference field on the user
- set taxonomy term reference field on content types (you want to use for group content)
- set up any view
Every site made with Drupal has its own custom requirements and you spend most your time as a drupaler altering other peoples implementations as there not quite right.
Dependency
This has a wonderful dependency on the following views module which is needed for providing the user field value of the group field.
https://www.drupal.org/project/user_field_value
Configuration Example:
1) Add a Vocabulary (lets say "teams") and ad a few terms. (which are the groups).
2) Create 2 roles (team admin , team member) optional (and don’t even touch the permissions page)
3) Add taxonomy term reference field on the user entity (to reference “teams”).
3B) make sure as admin user you have selected a team for development reasons
4) Create or edit A content type and add a taxonomy term reference field (to reference “teams”)
5) Install lw_groups and lw_groups_node
6) Place lw_groups block (Group Approve User Block) on the “/user/*” page with your role access.
6B) And see – hook_lw_groups_approve_access_block_link (optional)
7) Now we are ready to go to “/admin/config/lw_groups” and start configuring by filling out all required fields.
8) now you are ready to start making your views pages see example images in a nutshell you add the contextual filter to the user or content to the group fields you made in step 3 / 4
we suggest at least a group member page, and a group content page.
Project information
Seeking new maintainer
The current maintainers are looking for new people to take ownership.Maintenance fixes only
Considered feature-complete by its maintainers.- Created by taggartj on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
