Closed (outdated)
Project:
Organic Groups Menu (OG Menu)
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
14 Mar 2010 at 22:30 UTC
Updated:
13 Sep 2018 at 10:32 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
marcp commentedLooking at the code, for all new groups, you should get a menu created automatically.
For existing groups, you should be able to edit your existing group nodes and save them without making any changes -- a menu should be created automatically for you.
You can use Views Bulk Operations to automate this process -- it might take some digging to figure it out.
Comment #2
dtarc commentedYes, this is what I did, it worked well for me.
Comment #3
pyxio commentedI am trying to figure out the same thing. What I think is logical is that a menu item exists for every content type that can post into a group. Every new group should have a default menu with these items. It seems so basic I know it must be easy to do but I can't figure it out. If my group has content types news and jobs for example, how do i get a menu that has News and Jobs in it? Any advice would be much appreciated. Thanks.
Comment #4
bonobo commented@iteego - your question doesn't really relate to the original issue.
You solution, however, is not with OG Menu, but with the Views module. Set up a view that filters by content type, sorts by date posted, and has a group nid as the argument.
Comment #5
jide commentedHere is a patch that adds actions to create and delete group menus. It can be used with VBO.
Comment #6
jide commentedCommitted to CVS.
Comment #7
marcp commentedOne quick comment on the patch -- on this line it would probably be good to remove the em tag since the %node_title will get sent through theme_placeholder() or its override:
Comment #9
jeffschulerDid this actually make it into 6.x?
I don't see the code in 6.x-2.4 or 6.x-2.x-dev, and it looks like the commit that lists this doesn't actually add it...
Comment #10
jide commentedThis is because when og_menu module had been flagged as insecure, the dev branch was deactivated and since then commits on this branch were "ghosts", so it created a mess... I contacted the security team several times back then about this problem but did not get any answer. I'll try to find these commits on my local machine and recontact the security team about this.
Comment #11
jeffschulerThanks. FWIW, I was able to commit the patch to 6.x-2.4 and use it.
Comment #12
pfrenssenClosing, since the Drupal 6 version of OG Menu is no longer supported. If this issue is still relevant for the currently supported versions (D7 and D8) then feel free to update the version and reopen the issue.