Loading A User's Groups In Drupal 7

22nd May 2012 - 4 minutes read time

Note: This post is over a year old and so the information contained here might be out of date. If you do spot something please leave a comment and we will endeavour to correct.

Whilst working with Organic Groups today I had the need to load a list of the nodes that a user is connected to. After a bit of looking around in the source code I couldn't find a good solution on how to do this. So after looking around on Google for a bit I just sat down and wrote one.

Getting the group nodes that a user is a member of is quite easy as it turns out, but must be done in a number of steps. The first step is to grab a list of the group entity ID's that the user is connected through using the og_get_entity_groups() function. This can be used with no parameters (which assumes the current user).

// Load in the current user's group entity ID's
$groups = og_get_entity_groups();

Or you can load a user and pass this object to the function.

// Get the current user
global $user;
 
// Load in the current user's group entity ID's
$groups = og_get_entity_groups('user', $user);

The next step is to use these group entity ID's to load in the actual node entity ID's using the og_load_multiple() function.

// Load the entities object ID's
$groups = og_load_multiple($groups);

We can now finally start loading node objects using these group entities. This can be done in a number of different ways. The first is to loop through them and load in the node objects one at a time.

// Convert them into nodes, one a time.
$nodes = array();
foreach ($groups as $group) {
  $nodes[] = node_load($group->etid);
}

An alternative is to loop through the list of group entities and load all of the node entity ID's into an array. This can then be passed onto the entity_load() function.

// Load all of the nodes with one function call
$nodes = array();  
foreach ($groups as $group) {
  $nodes[] = $group->etid;
}
$nodes = entity_load('node', $nodes);

Using entity_load() is a good alternative as it means that you can use the conditions parameter to only load certain nodes without having to load each node in turn. In the following example I only load nodes of the type 'club' within the $nodes array.

// Load all of the nodes with one function call 
$nodes = array();  
foreach ($groups as $group) {
  $nodes[] = $group->etid;
}
$nodes = entity_load('node', $nodes, array('type' => 'club'), FALSE);

Update:

So it turns out that og_load_multiple() is no longer a part of Organic Groups, at least in the 2.x version. An alternative to this is to use node_load_multiple(), which will load all of the nodes as node objects. So, to load all of the nodes connected to a user in one go do the following:

global $user;
$groups = og_get_entity_groups('user', $user);
$groups = node_load_multiple($groups);

Be careful though, as if a user is a member of lots of groups this code will load all those objects.

entity

Drupal

Drupal 7

Add new comment

Related Content

Drupal 9: Stubbing API Modules For Fun And Profit

If you've been building websites sites for a while you will realise that no site lives in isolation. Almost every site you build integrates with some form of API, and this is especially the case for the more enterprise sites where data is often synchronised back to a CRM system or similar. Drupal's hook and service architecture means that you can easily build integration points to that API to pull in data.

Drupal 9: An Introduction To Services And Dependency Injection

Drupal 8 and 9 are built upon services, with many parts of the system available through dependency injection, so it's important to understand the concepts. Services are a way to wrap objects and use dependency injection to produce a common interface. They are powerful and are used all over Drupal to do pretty much everything.

Drupal 9: Selecting Machine Names For Content Entities And Fields

Naming things is hard^{[citation needed]} and there are a lot of things that you can name when configuring a Drupal site. Picking the right machine names for the different parts of Drupal can make your life easy in the long run. Changing labels is simply a case of tweaking the label in the interface, or through configuration updates. The issue is that once you decide on a machine name for something in Drupal it's pretty much set in stone forever.

Drupal 9: Configuring Drupal To Be An Identity Provider With SimpleSAMLphp

I have previously talked about configuring a Drupal site to authenticate against a remote SimpleSAMLphp install, but as Drupal is an excellent user management system I wanted to turn it around and use Drupal as the identity provider. This means that Drupal would allow users to log into other systems using their Drupal username and password by leveraging the power of SimpleSAMLphp.

Drupal 9: Configuring Drupal To Authenticate Against A Remote SimpleSAMLphp Identity Provider

I have previously talked about installing SimpleSAMLphp using composer, so the next step is setting up the system to actually provide authentication against a SimpleSAMLphp system. As I spend a lot of time using Drupal I wanted to set up the authentication with Drupal and SimpleSAMLphp in order to see how things worked.

First, let's define a couple of terms that are important to this setup.

Drupal 9: Creating A GET Form

I've been building Drupal forms for a number of years so I'm quite familiar with to putting together a Drupal form using the FormBase class and the form API. When I attempted to create a GET form this week I realised that there is actually quite a bit to think about. All forms are build using GET requests, it's the submission that I am specifically talking about. By default, forms in Drupal use POST requests to submit their data, and although it is possible to convert a form to use GET to submit data, it isn't well documented.