I don't know if I'm expecting this module to do something it can't or I just haven't figured out how to make it work, but here is what I'm trying to do:

I have a list of Groups and Subgroups like this:
World
-->United States
----->California
-------->Bay Area
------------>Town Names
----->New York
-------->Capital District
------------>Town Names
-------->Long Island
------------>Town Names

When some one registers they have to join a Town Name Group, and I expect them to be automatically subscribed to all Parent Groups above them up to the World Group. But this is not what happens. A new member has to manually subscribe themselves or an admin has to subscribe them.

Am I expecting too much, or is not working the way it should?

Either way, is there away to accomplish what I'm trying to do?

Thank You,
Steve Wickham

P.S. On another note, it appears that I can make circular sub-groups. I.e. I can take the structure I showed above, and make World a sub-group of the Town Groups.

Comments

ezra-g’s picture

There is a patch in progress at http://drupal.org/node/145333 to allow posts to propagate to parent or child groups, but it only propagates to two groups beyond the current group, to a group's grandparents.

Currently, the module does not include functionality for propagation of posts to parent or child groups.

pjo’s picture

Agree with wickwood, I would need a functionality like that too. Have I misunderstood this or is your patch ezra-g for a submitted node to be displayed in parent groups? Me and I think wickwood too, wanted to automaticly make a member of a subgroup also to be member of parent groups.

Nijip’s picture

Very exciting!!! is there any chance of getting the patch released as a Dev version... only because i'm not very smart and don't know how to patch (and find the patch instructions difficult to understand)

ezra-g’s picture

Status: Active » Closed (duplicate)

Marking as duplicate of http://drupal.org/node/145333.

Steel Rat’s picture

Actually this isn't a duplicate of the linked post. The issue is about members of a group, not the nodes in a group.

LanceLight’s picture

Yes this is a completely different issue from http://drupal.org/node/145333. The dude said nothing about "posting nodes". He mentioned that the MEMBERSHIPS (show the groups menus when the parent group is selected, etc) are not propagated which is actually a fact. They do NOT add you as a member to parent groups. This is a feature that has yet to be developed for this module and one I had to code up myself as well. When you click on a parent group it will ask if you want to JOIN that group which is a red flag that tells you that this module does not have the expected behavior of adding people to the hierarchy as a member to all the parent groups. I dont think this should be a default feature but rather a selectable option on a per group basis or a site wide basis or not at all. My own site has 3 options, (1)Propagate if parent is marked as inclusive, (2)propagate in all groups, and (3)never propagate. Currently 4 of my sites use option 1 and 1 site uses option 2 and 1 site uses option 3.

ezra-g’s picture

@Lancelight: If you've already coded this feature up, could you please contribute it back as a patch to this module?

Thanks.

LanceLight’s picture

Hmmz yes I could do this. Is there a specific version it should be patched against like a CVS version anywhere or would the release version be good enough.

ezra-g’s picture

This should be patched against CVS HEAD, which at this point is the same as the release version.

ezra-g’s picture

Also, perhaps this is actually a duplicate of a different feature request: http://drupal.org/node/234474 ?

LanceLight’s picture

Havent read any of the feature request threads yet but the one you pointed out, the original poster is asking for this specific feature yes. I think the patch I can create would satisfy that request nicely. I will go clean up the code, comment all the additions/changes and put up a patch sometime today for this.

ezra-g’s picture

Great. Could you please post it at http://drupal.org/node/234474 as opposed to on this issue?

Thanks!