When I click on a group, I see the group menu - Home, Events, Blogs, Wikis, etc.

When I click on blogs I get a list of the blogs (powered by views) and I still see the group menu - Home, Events, Blogs, Wikis, etc.

When I then click on a blog post to read that blog, the group menu - Home, Events, Blogs, Wikis, etc. - is not there anymore, I now need to use the back button to get back to it. This is a pain if I have clicked on a blog title and then spotted an interesting event from the sidebar, and then a poll from the sidebar. Now, I'll have to hit the back button a number of times to find a page with a group menu - Home, Events, Blogs, Wikis, etc. - so I can choose my next category of what I want to look at.

So, in short, the group menu works on the group homepage and any views associated with group_nodetype_tab, but not on individual group nodes.

Comments

markconroy’s picture

Looks like I am not the only one asking for this:
http://commons.acquia.com/discussion/groups-tab-menu-does-not-show-group...

lightsurge’s picture

Subscribing.

I posted a similar issue, not only are the group tabs lost, the breadcrumb context of a post is too #1287760: when in a group, and travelling to a node from a content type tab, content type should be in breadcrumb as well as node

markconroy’s picture

I just disabled breadcrumbs since they are so badly configured. This issue though is a must for a commons site, why would anyone want the group menu to disappear on a group page?

lightsurge’s picture

One way of easily achieving this would be:

Instead of having group node teaser views (i.e. group blog, group discussions, group events) link to the full node (i.e. node/[nid]) instead to link to a View which lists just that 1 node in full node view (i.e. node/view/[nid]). This way all tab menus established by the group views could be maintained?

Is this a bad/lazy way of doing it?

markconroy’s picture

That sounds interesting, but doesn't that mean creating a view for every node? I've about 2500 nodes at the moment and would expect that to reach about 50,000 in the next few months.

lightsurge’s picture

It would probably mean creating a view display for each of the group content views, which would display a single full node based on an NID argument.

I tried this though with mixed results. I think it would probably better for these tabs to be 'themed in' somehow (we already have a node theme template for nodes posted in groups).

markconroy’s picture

Version: » 6.x-2.4

Any update on this?

How would such a view look, if it isn't possible to force the menu to stay present at the top of nodes posted in groups?

I really can't believe this is such an issue.

Some solutions I tried:

Use Menu Token module to create a new menu to place in a block and then remove all these group tabs - problem: token menu only uses "Global Tokens"

Create breadcrumbs to show the hierarchy - problem: works fine, but then the breadcrumbs are so terrible that on my page that lists all sub groups of the last parent, all other groups are also listed (so I've a bread crumb of about 2,500 items BEFORE I get to see my page). l

Use Token Filter to create a block with a list of these menu items - problem: the filter didn't take to blocks (as far as I can see) - then my harddrive bust on me!

Now I'm thinking of cloning the views that are providing these tabs and setting them to a custom menu that will display in the sidebar and then disable these tabs. Fingers crossed.

markconroy’s picture

Ok, tried my last solution from above, but am told: "Views cannot create normal menu items for paths with a % in them.", so the menu link can't be dynamic and I don't want to create 2,500 individual menus/blocks for every group we have created.

Pleeeeeeeeeeaaaaaaasssseeeeeeee!!!!!

lightsurge’s picture

Currently the tab menus are created by Views so the only way you could have them display on a node would be if the node were also being displayed within a view. That is, you could add a view with an argument of 'nid' then change the links to the nodes in the group content views to link back to the new view but with the nid as argument... or if you wanted the content type tab to remain 'active' while viewing content of that type, you could try adding a display to those views instead of using a separate view.

Then you'd have to use some custom PHP to set the page title to the node's title, and load and print the node (or use something like http://drupal.org/project/viewsnodefield).

This is not really a good solution though for a variety of reasons. You might have to wait until somebody comes up with a totally different solution for group menus.

Breadcrumbs with content type in them are fairly easy to do though... I have this going on my site and might submit as a patch on #1287760: when in a group, and travelling to a node from a content type tab, content type should be in breadcrumb as well as node at some point. Also sounds like you might still be suffering from #1265636: Breadcrumbs Displaying all sub-groups from another parent

lightsurge’s picture

I quite like the idea of using taxonomy_menu for this (perhaps combined with hierarchical select for usability).

markconroy’s picture

Thanks for the thougths lightsurge,

I don't want to create a view for each node, given that we have about 10,000 nodes at the moment.

To get around the breadcrumbs issue, what I am doing is setting a "regions" taxonomy term to each of the 2,500 groups and then creating a new view to only show groups of this type, and then use custom_breadcrumbs to do what I want to the breadcrumbs.

lightsurge’s picture

You would only need one additional view. You could

  • clone, say, the group_tab_blogs view and call it something like group_tab_nodeview,
  • remove the sort criterias and filter criterias apart from published and in current group,
  • add a node nid argument set to hide the view if the argument is empty,
  • remove the fields and use something like http://drupal.org/project/viewsnodefield to add the full node as a field
  • change path to node/%/content/%/view
  • change text of menu tab to something like 'View'
  • alter the other group_tab views such that node title links to node/group_nid/content/nid/view (rather than directly to the node as currently)

This is just from memory, I might have missed bits to make it look right and function securely

markconroy’s picture

Wow! Thanks for that. I'll give it a shot tomorrow. That looks very workable (if you happen to have a copy of a view like that, the php would be really appreciated - I haven't used "arguments" in views before (except by following a recipe somewhere)).

Thanks again ... great help.

lightsurge’s picture

You don't need a php argument here, just a simple one. It's just like adding fields, you'd just add node nid to arguments, and pretty much the only customisation you'd need to make is to set it to hide the view if there's no argument, rather than display all.

markconroy’s picture

Thanks. I'll try that ... fingers crossed.

sparker888’s picture

@ Mark C

Did you have any success with this? Can you report back any more details on creating such a view? That would be helpful to myself and perhaps many others with this issue (particularly in Drupal Commons).

markconroy’s picture

I haven't tried it yet, got fierce busy, and have just been using Custom Breadcrumbs module instead to show the breadcrumb trail that I want.

If I get around to it I'll certainly report back on the steps I made (guessing it will look something like the "Group Node" view.

avpaderno’s picture

Title: group clone » Make Group Menu Display on all Nodes belonging to a group
Version: 6.x-2.4 » 6.x-2.x-dev
Issue summary: View changes
Status: Active » Closed (outdated)

I am restoring the original issue's title, and closing this issue, since it is for a Drupal version that is no longer supported. Furthermore, this distribution does not have releases for supported Drupal versions.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.