#Organic Groups

I am using Profiles 2 and Organic groups.

I was successful in listing users via views > Users.

I am using "profiles 2" module to collect and store details of users rather than the core drupal user management.

I have created few groups using "organic groups" module.

My question is how to list all the "PROFILES" (created via profile2 module) of members belonging to a group using views ?

Thanks....

Hi,

Here's what I'm trying to do. Any help would be greatly appreciated!

Upon saving new content, set a user reference field with all of the users that belong to the group content's audience that have the administrator member role.

Use case: We're using organic groups to manage committees. Then, we create evaluation nodes of these committees. Because the committee (group) membership changes, we want to save the group administrators to a user reference field within the evaluation node.

Here's what I'm trying to do with out the check on group member's user role.

Rule
Event:

Hi,

We are using content profile at time of registration. After reviewing user details we want to assign user with some special previllages (for that we have role say master). Now when we assign role to this user then with help of OG module we would like to create one group with title of user name. We tried to do it with Rules module but we are not getting it. can you help us how to do it.

We have following steps in rules.

Event : User account details have been updated

IF
User has role : masters (updated users)

DO
Load updated users content_profile

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?