I've Installed the Module for Druapl 6.x, Now What?

You need to use the book fieldset on the node. That's confusing and we're working to eliminate it. See #337808: Eliminate dependence on book.module for the latest on how we're going to deal with this. We apologize for the confusion.

I'm still lost. The only way I have an idea as to how this is supposed to work is by having a copy of the DrupalEd distro (D5) with subgroups installed. In that example, there is a tab at the top of the group create/edit page for subgroups where you can set the parent. When I added the og_subgroups module to D6, I see no subgroups tab on a group's create/edit page. and I find no other way to set the parent.

I'm guessing based on this thread that I have defined my Group content type incorrectly. You said "you need to use the book fieldset on the node" is confusing and you're right - because I have no idea what you're talking about. Do you mean that one needs to define the group node content type to use the book fieldset? If so, how does one do that (searching drupal.org on "book fieldset" is not helping me)?

Thanks

Same issue here. Why no response?

In the group node you should have the book settings (i.e. book fieldset), which through there you set the hierarchy of the groups, the same as you would set the hierarchy of book pages. If you don't see you the book fieldset, then go to the book module settings and make sure your content appears as available for books.

Hi, Thanks for your response. I would like to offer my services in helping out with this module testing/small coding/readme.txt

You are most welcome :)

Pm me with what you require.

I'm reactivating this issue with the hope that it will serve as an instructional thread for those of us trying to get a handle on how to implement Subgroups for OG. I would like to take the results of this thread and create a definitive help page on how to configure Subgroups for OG.

I'm attempting to use OG combined with OG User Roles and Subgroups for OG. I have OG and OG User Roles working nicely together (admins and members see and don't see what they're suppose to.) In my case the parent group content type is called "company". I now need to create multiple "location" subgroups for each company group node with Subgroups for OG. I have my parent/child relationships working and permissions set correctly so that admins have the ability to create location subgroups. I create a location subgroup node and it appears as a link on the company group page. Clicking on the link takes me to the location node, but this is where things begin to get somewhat fuzzy. How are the hierarchical permissions enforced?

Here's my particular need illustrated. I would like to grant all members access to a parent company group node and also one or more child locations subgroups. For example:

Company #1
- Location #1
- Location #2
- Location #3

Company #2
- Location #1
- Location #2
- Location #3

All company parent groups and location subgroups are private. So for example when a member is added to Company #1 they must also be added to Location #1. Members of Location #1 will not know of the existence of Location #2 and Location #3.

I was under the (perhaps false) assumption that membership to each child subgroup node could be controlled individually.

I would appreciate hearing from anyone who has information about how Subgroups for OG is designed to work and if my above scenario is possible (in whole or part.) If anyone knows of a good resource (whether on-line or in print) please post that as well.

Thanks in advance,
John

Hi John,

Count me in! I've only just got OG Subgroup working (I think!) I'll report back here after i've investigated it.

Cheers.

Thanks for your question, @Bacteria Man.

Unfortunately, the Drupal 6 version currently does not support multiple parents for the same node as you've described. We're working to re-architect it so it is more flexible. You can follow progress in http://drupal.org/node/337808 .

Thanks!

Ezra, thanks for your response and excellent work on this very important module.

I gather from the discussion contained in the thread you referenced it sounds like you've hit a wall in trying to bend and contort the book module to meet the requirement. The whole using-books-to-mimic-subgroups approach is creative and admirable, but is ultimately awkward and unintuitive. From a development perspective there's no shame in rolling in some of the core book module code in order to achieve a greater level of flexibility.

My application greatly depends on the hierarchical structure described in my previous message. In a perfect world child subgroups would look and behave just like parent groups.

Please accept my sincere appreciation and encouragement to keep pushing in this direction. I'm happy to contribute to the discussion and obviously help test and debug.

Thanks,
John

Hi Guys,

The time to report back has come....sigh!

Having spent some time now investigating the OG Subgroup module; I guess I just don't get it!

Firstly I made sure OG was working correctly, with group nodes created for city1, city2, city3 (gids[]=1, gids[]=2 and gids[]=3, og forums and various group content types) So far so good.

From the myriad of possible settings, here's what I ran with:

In admin/og/subgroups for Content propagation: I chose Children, same for Propagation direction:

In admin/book/settings for Allowed book outline types: I selected Forum topic, Group post, Group node, Group news (My group content types) For Default child page type: I tried Group node (and others)

I then navigated to the group node for city1 and created a new book (city1) I the added child pages Group1 Group2 and Group3 Activating the Subgroup Navigation block showed:

City1
-Group1
-Group2
-Group3

I thought I had cracked it, so I navigated to Group1 and noticed that the default OG Group Details Block still reported gids[]=1 for all selections. I was hoping for gids=[]1 && Group1, Undeterred I created 3 posts:

First post: node/add/grouppost?gids[]=1 In Book Outline I chose City1, and in Parent Item I chose Group1
Second post: node/add/groupost In audience I chose City1 and same as above
Third post: node/add/grouppost nothing for audience and then Book outline as above

Going back to Group1 I now see teasers for my 3 posts, navigating back to city1 group node, my subgoup navigation block now looks like a dogs dinner:

City1
-Group1
-Test post3
Group1
-Test post2
City1
-Test post1
-Group2
-Group3

This all seems just far too complex, all I require are subgroups that users can join and post in and out of.

I can only hope that your intended re-design is going well and my offer of help testing/documentation still stands.

I doubt very much any of you guys will have time to analyse my issues but if there is a glaring gap in my logic/approach please point it out, as this module is driving me mad!

Thanks...

ludo1960, thanks for sharing your findings. They are, unfortunately, pretty consistent with my experience.

In the absence of pure subgroups I'm beginning to think that using Taxonomy Access Control might be a better way to go. One could mimic subgroups by assigning terms to group node content.

Hi John,

Thanks for you reply, I too was thinking about TAC, but I don't want to dive into just yet.
The guys here..Moshe, ezra-g & Co are true Drupal Alumni. I have got to know my way around Drupal and I refuse to be beat by this module.

Moshe. Put me out my misery; does this module "Do what it says on the tin" or am I missing the bleeding obvious?

Ludo.

PS How's the re-disign going?

OK, using the current mechanism for creating subgroups, let's say that I will create my own code in the nodeapi hook to automatically insert the parent item for a new subgroup being created. Let's say I know the parent group node. Can someone tell me the functions I need to call in order to get this parent group node inserted as the parent item for the new group node being created?

My goal here is to set up the subgroup hierarchy automatically by passing the required info in the url when creating a subgroup, and using hook_nodeapi to actually set it when the subgroup node is saved.

Thanks for any assistance.