Menu parent item is empty if user belongs to only one group.

Did you select the "Enable for OG Menus" setting on the content type?
Which type of widget are you using?
Is this on content creation or on content editing?
Are OG Menu permissions granted globally or on group level?

On content creation you need to have an OG context set from the url., and configure the og widget to listen to it.. are you doing that?

(sorry for the questions, just have to be sure before i start testing this)

Can you try latest dev and tell me if the problem is still there?

I'm afraid it's hard to say whats going on without having a look at the og, og_menu and menu related tables in your database..

Beating a dead horse here and I apologize. I just wanted to confirm this is still an issue even with 7.x-3.x-dev. I am running OG 7.x-2.9. If a user belongs to only one group the parent item dropdown is empty.

@westonpay
I'm 100% sure this works when a user only has one group.

are you sure it is not permission related?
How/where are users given access to the OG (!) menu ?

Hi,
I'm using version 7.x-3.1 and I'm experiencing this issue as well.
I'm thinking that this is a javascript issue. Since the parent menu selection is triggered by selecting a group within the Groups Audience field, users can’t select a parent menu item because there isn’t a chance to actually select a group if the user is only part of one group.

see my previous post.
there is a configuration reason for this, but without knowing your exact config I cannot help

A work-around that worked for me was reconfiguring the Groups Audience field widget from "OG reference" to anything else and then back to "OG reference". Doing this messed with the field settings a little bit so I had to make sure my field was configured correctly as well.

Before, the Groups Audience field was being automatically populated by the only group the user was a member of. Now instead, after doing that reconfiguration, the Groups Audience field now shows "Select a value" and the user needs to select the group. (See attached image)

Not sure if this sheds any light as to why I was experiencing this problem.

there must have been something different then in your field config

if you have a backup and could roll back, this might help people experiencing this issue

A key part of this looks like the cardinality setting for the OG group ref field. Changing it from 1 to unlimited seems to have triggered this on www.drupal.org. The widget as the affected user sees it is a single select field, but og_menu.js is processing it as cardinality != 1 and is looking for a multi-select field.

Drupal.ogMenu.selected ends up being something like [3, 0, 2, 5, 7, 6, 8] instead of [3025768]

MR !1 checks the multiple attribute of the HTML element instead of trusting the select element to match the field cardinality.

@drumm
Seems like a proper solution, and nice to see some light on an issue from 2014
I don't have access to any D7 sites with OG Menu, or any development environment with a proper configuration for it.
Could you provide exact steps to reproduce the issue? (field and widget setting and whatever else is relevant?)

Thanks in advance

I spotted where the single/multiple select list switch happens: https://git.drupalcode.org/project/drupal/-/blob/7.77/modules/field/modu...

I don’t have a clean development environment with all the steps to reproduce. I think the key parts are:

• The OG group reference field must have cardinality > 1, so the node can be in multiple groups.
• The user must have access to one group, so they only have one option.

(We do have www.drupal.org’s configuration exported at https://git.drupalcode.org/project/drupalorg/-/blob/61514c71f32a3e85e098..., but I don’t expect that to be too helpful as the module has a lot of unrelated baggage.)

A new 7.x-3.3 release is coming, thanks for your contribution!