Organic groups

Hi,

I was looking for a way to retrieve a custom field from a group in a view?

For example, I have my Group content type in which I added a custom field (say the «Group Color» field).

Then, I wanted to build a view in which I could show the current node's group «Group Color» field. I was able to retrieve the current node's group ID, but not the custom field.

I built the view showing any type of node and used the OG Groups relationships to ge the current node's group ID.

Anybody has an Idea on how to do this?

Thank you,

Jean-Louis

We are using Drupal to create a custom content type with it's own module along with a site to support that. My boss wants to create a "viewer" user role for groups, where such a member can view the content associated with the group but not create content for that group. This would only make sense with private groups. I have looked into the existing settings for Organic Group User Roles and Permissions and there is nothing to control whether someone can create content associated with the group. Do I have to go in through the API to create this?

I am completely stuck after upgrading my website from Drupal 6 to Drupal 7 and I am desperately looking for answers to two questions:
1/ How can a group manager add new members to his group? All screens are working properly (I suppose), even the screen for the group administrator to add new members, but there are no new names in the list of members.
2/ I have created a group calendar, but now there on each screen is a tab for a calendar and that - offcourse - is not the intention.

Hello everybody

I'm using OpenAtrium, I think it's 1.0, but not sure.

I need a user with special profile to access a node into a group without being group member. Is that possible?

In short my code gives groups and "my_content_type" a grant called "my_realm" with gid 1.
hook_node_grants() gives each user with "my_special_role" a grant called "my_realm" with gid 1.

As far as I know that should give access user to node, isn't it?

I added this code, but it's not working:

<?php

/**
* hook_node_grants()
*

I am wondering if the following use case is apropriate, feasible off label, or should not be done with OG7.

Use Case Example
A national club runs a web site and uses OG groups to manage membership in local, affiliated clubs. National members may (or may not) be members of a local club by joining their group. Via Rules, this changes where they pay dues, etc. So far so go.

The issue is that users may be members of more than one local club but only the first one they joined is where we send their membership packet, collects dues, etc.

To summarize, is there a way to identify (and integrate with Rules and Views) a "primary group" for the user?

I've set up this group to try to get some help fixing the Notifications module which is important for Organic groups. The issue I hope to fix in this new group doesn't seem too complicated, but I don't have a lot of experience with the innards of Drupal so I'd find it hard to do on my own. So I'm hoping for a bit of help from others.

I have several years experience setting up quite complexmulti-lingual sites & using views a lot. I know some basic php (unfortunately I know asp better - the way things were at the time), but I've never got into Drupal module code at all seriously. The languages I use are English & Spanish.

The task

Notifications does support language. When the process is run from /admin/messaging/subscriptions/queue by using "Run process" then both the language that Notifications uses for the email texts & the language negotiation of the URLs is translated. So far so good.

However, the problem is that each individual message ignores the users language and applies in the language that /admin/messaging/subscriptions/queue is using.

So the question is to insert some code into the module at the point in the process where it works on the messages for each user so that everything it does at that point is in the user's language.

I'm going to start poking about in the code to see if I can make sense of it, but if anyone can give me an early indication of what I'm looking for that would be a great help.

Hello folks, I've been trying to get a handle on my perspective as the latest maintainer of OG's 6.x branch. There is an entire, gigantic issue queue with ideas of what's wrong and where folks would like it to go. As I've tried to curate the queue, I've come to realize there should probably be some kind of discussion.

OG6's sun has already started to set, but it remains in use on thousands of websites. It's biggest challenges are not in exploring new features, but in supporting existing websites and new, stability-critical D6 websites by cleaning up the many warts: unexpected or incomplete behaviors, usability-challenged workflows, performance improvements, low-impact integrations with common modules (Features, etc), and if possible more thorough coverage by automated tests.

As mentioned in the Issue Queue, 6.x-2.2, with a slow year of enhancements and bugfixes, is almost ready. All that waits is fixing the broken tests and reverting Notifications 4.x support back to the more stable, known Notifications 2.x line.

What should be done after that?

This is a question pertaining to OG 7.

I am trying to show a pane (using Views and Panels) which will include fields from the user profile of the Group Manager on a organic groups page. I am trying to determine the best way to filter only the OG manager and not any one else from the group (currently everyone appears in the block).

I've tried many different relationships in Views 3 and various filters based upon those relationships, but so far nothing :(

Any hints?

Thanks!

kevin

now i want to create a groupe with admins user:
<?php
global $user;
$node = new stdClass();
$node->type = 'group'; // Change this to group node type name.
$node->uid = $user->uid;
$node->title = t('Mon groupe'); // Change title generation
$node->body = t('Body'); // Change body generation
$node->og_description = t('Group description'); // Change group description generation
$node->og_selective = OG_CLOSED;
$node->og_register = OG_REGISTRATION_NEVER;
$node->og_directory = OG_DIRECTORY_CHOOSE_FALSE;
$node->og_private = 0;
node_save($node);