I'm building what I presume is a pretty common use case:
A view to attach to a node, which shows all the child menu items of the node's corresponding menu item.

What I *thought* should work was:
1. create a "Menu tree" view
2. relationship for "menu: parent menu link id"
3. contextual filter for "menu: node id", using the relationship from #2, with "provide default value: content id from url"

What *actually* works is:
1. create a "Menu tree" view
2. relationship for "menu: parent menu link id"
3. contextual filter for "menu: node id" (no relationship), with "provide default value: content id from url"

I put up a pastebin of the latter: http://pastebin.com/u2GjmWG7

I'm happy to have something working, but this doesn't actually make sense and I'm worried about it breaking for future versions.
Filing as a bug report for now, but if someone can explain *why* this works, then maybe it should be a support request.

Comments

markhalliwell’s picture

Hmm, this could very well be a duplicate of #1933128: Tokens not working. I haven't had a lot of time lately to address this issue, but pretty sure these are related.

markhalliwell’s picture

Title: Weird relationship + contextual filter handling » Support menu relationship + contextual filter handling in views
Category: bug » feature

The token issue was fixed in commit f8d375e.

However, looking at your pastebin, I'm curious to know what module you're using to get these menu relationships and contextual filters.... I didn't even know this was possible.

aaronbauman’s picture

markhalliwell’s picture

Title: Support menu relationship + contextual filter handling in views » Support menu_node_views module
Status: Active » Postponed (maintainer needs more info)

Ok, I'm pretty sure that the commit I made should fix this, since you're using a contextual filter in the view (for the menu item node id) and that's being passed via the menu item settings as a token right?

Try the latest snapshot: http://drupalcode.org/project/menu_views.git/snapshot/refs/heads/7.x-2.x.tar.gz and see if this is resolved. If not, I'll have to postpone or close as won't fix as I don't have the time to support every module integration. Patches are always welcome though.

markhalliwell’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (fixed)

No response, assuming it was "fixed".