Closed (fixed)
Project:
Views (for Drupal 7)
Version:
6.x-2.0-rc1
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
23 Jul 2008 at 18:20 UTC
Updated:
29 Dec 2010 at 11:58 UTC
I have set up several views as tabs for 1 default tab set up as the parent. All paths for the tabs are set up as foo/bar with the parent tab being foo. I can type in the url for any of the child tabs and the view displays but no tabs are shown. When I go to the parent's url, neither the view nor the tabs appear. I can not figure out what I am doing wrong. Any help would be great.
Thanks!
Comments
Comment #1
davbusu commentedyep...same prob here
Comment #2
alexpottI've just had the same issue - and it seems it's all down to my config!
Here's how I resolved my issue.
I have two views set to display as pages... the default tab is a list of nodes and the other tab is a calendar view.
The list view got the menu settings "default menu tab" and I set the menu parent to "normal menu item" with a value of "live"
The calendar view got the menu setting "menu tab"
What proved to be vital to make the tabs appear was the path settings...
the list view path was "live/list" and the calendar view was "live/calendar"... I had presumed the default menu tab should have a path of "live" but I was wrong...
Now when I navigate to "live" everything works as expected.
Hope this helps
Alex
Comment #3
zilla commented@alexpott - THANK YOU - you just answered a question that was making me nuts for the past couple of days...could not remember how to set the root for the menu, the logic is odd...but now working like a charm!
Comment #4
merlinofchaos commentedI believe this is now a Documentation task to ensure that the menu help page thoroughly documents this situation so that, in the worst case, we can point people who have questions to it.
Comment #5
zilla commented@merlinofchaos -i'm guessing that this is one of the most common issues people encounter when creating a tab, not realizing that the path for default must be named yoursite.com/yourview/viewhometab - and understanding that it goes to /yourview (without using /viewhometab) - but that all pursuant items must in fact go to yourview/viewhometab/yournextview
i may scribble up some documentation for this particular item as i see quite a few questions about it! obviously screenshots make the most sense so will first post in these support forums for review and feedback (i'll be creating some views later today so will capture screenshots of all of the tabs in creation and explain how the root was setup etc)
hopefully it will be decent enough for documentation (meaning a version that also works without screenshots for [perhaps] the readme.txt in a 'quick start' sort of way
Comment #6
merlinofchaos commentedSuch documentation would go here http://views-help.doc.logrus.com/help/views/menu in the advanced help.
That is help/menu.html -- a patch against this file makes my life very easy. (With advaced help installed you can visit http://yoursite.com/help/views/menu to see your version of it)
Comment #7
zilla commentedthanks - can advanced help support menus? i'm thinking of making a totally non-technical language version of this (like a views-for-dummies kind of thing, a visual quickstart so to speak)
Comment #8
merlinofchaos commentedIt supports a book-style hierarchical page structure, which I *think* is what you want when you ask if it supports menus.
Comment #9
zilla commentedsorry, meant photos! (not menus, duh)
Comment #10
chrisschaub commentedThere is a bug related to parent / child tabs. Moved comment to its own bug report:
http://drupal.org/node/336935
Comment #11
vivianspencer commented@alexpott - amazing dude, I was going around in circles with this issue, thanks
Comment #12
esmerel commentedComment #13
iamjon commentedI spoke with alexpott about this on irc.
It seems that current views doc offers an explanation on how to accomplish
alexpott suggested that maybe adding screenshots would clear things up further.
Here is the current entry:
http://views-help.doc.logrus.com/help/views/menu
Comment #14
iamjon commentedI'm marking this as closed.
Please feel free to reopen to continue the discussion.