Greetings,

I have been using the multigroup module for almost a year now and it's been great. Recently I ran into an issue when I had a user reference field in a multigroup. The multigroup is part of an organic groups form that posts directly into a group.

The user reference field utilizes a view to create the user list, which has an argument in place to filter users by those who are subscribed to that organic group. When I create the form the first multigroup works great and filters by the members of the group, but when the next multigroup set is added all the values for that user reference field disappear for both multigroup sets and the only option is none.

I attached two screenshots with the first being the case where the og argument worked and the second where the user reference field options disappear.

Is there a configuration step that I missed in setting up the multigroup?

Thanks so much!

CommentFileSizeAuthor
#2 multigroup_og_context.patch1.36 KBsullix
multigroup_second_user_reference.png21.71 KBlegendaryintern
multigroup_first_user_reference.png19.12 KBlegendaryintern

Comments

sullix’s picture

sullix commented

I am very interested to know how to manage this. I experienced the same issue with a "OG Context" argument in a node reference field/views.

sullix’s picture

sullix commented
StatusFileSize
new multigroup_og_context.patch1.36 KB

I've just found the solution: set the og context also in the add_more_js page.

Put the following code in the content_multigroup_add_more_js function (content_multigroup.node_form.inc):

<?php
  // OG context : first checked group (node edit form)
  if(module_exists('og') && isset($_POST['og_groups'][0])) {
    og_set_group_context(node_load($_POST['og_groups'][0]));
  }
?>
sullix’s picture

sullix commented
Status: Active » Patch (to be ported)

Patch attached to comment #2.

karens’s picture

karens commented
Status: Patch (to be ported) » Needs work

This is not a 'patch to be ported', it needs review. And it is pretty specific to OG so I'm not sure it's the right approach. But the starting point is to see if there is even still a problem in the latest code, now that the nested fieldgroup patch has gone in.

tammo’s picture

tammo commented

I ran into the same bug. Did you ever get around this?

I need this for the following use case:

I have sessions that belong to groups. Each group (no OG groups, just a content type) has several persons (also just content type, no user) that reference to the group and that can be present at a group session.

When I create a session, this session has the NID of the group in the URL ( .../node/create/session/883 where 833 is an example of the nid of the referring group) and this is used as the argument for the view that calls the persons that can be present (only persons that reference to the group that this session is created for).

This used to work great when using the CCK 2.x with NO fieldgroups. But when I wanted to use fieldgroups where for each person present also a location in the room was to be recorded, this failed, just like the first poster of this thread found out. I am desperately looking for a solution.

jvieille’s picture

jvieille commented

I have this problem too.
It used to work in the past, but for some unknown reason, the group context is now lost as soon as a new fieldgroup is added - exactly what happens to #1.

Hard setting the group in the views argument makes it working, so It really looks like multigroup kills OG context.
This explains why #2 patch does not work for me.