Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.According to the help text in the Default Menu Tab section of Views, when using a tab, I should be able to create a tab and have the parent be a menu item that already exists:
Select type of parent item to use for this default menu tab. You can either specify the parent should be a tab (the default), a normal menu item, or to use the menu item that already exists at the specified URL. For example, if the URL for the default tab is 'tracker/all', then 'tracker' would already have to be a valid menu item to use this final choice.
What I want to to is have a page node as the parent item, and then three tabs (one for each of three views) and child items on the page. So as I read this, then if I have http://mysite.com/mypage, I should be able to create three views with URLs of mypage/view1, mypage/view2, and mypage/view3, and be able to see them when I go to mysite.com/mypage, assuming that I've set the Parent Menu Item Type option to "Already exists (don't create)".
My problem is, this doesn't work. I have created a page with the url of resource-center, and three views with URLs of resource-center/basic (set as the default tab), resource-center/best-practices, and resource-center/technology. If I go to mysite.com/resource-center, all I get is the page with no tabs, and if I go to mysite.com/resource-center/basic, all I get is the tabs with no page. As far as I can tell, I"m setting it up right. Is there something I'm missing?
Thanks.
Comments
Comment #1
wonder95 CreditAttribution: wonder95 commentedChanging to Views Tabs queue.
Comment #2
nedjoThe "tabs" in views tabs are not the menu items described here.
This looks like a support request on the views module. Moving there.
Comment #3
NikLP CreditAttribution: NikLP commentedI think the problem is that when you create a tabbed interface, there is some expectation that the "root" page is going to be defined as a "default menu tab". I have had similar problems myself but with views 2. The situation that you describe cannot, as far as I can tell, be easily created using Views out of the box. That is, the "Page as the default" setup is not catering for the expected "default menu tab" as I described.
You need to have a setup like this:
- myview/view1 (is the default item, the "default menu tab")
- myview/view2 (is a menu tab item)
What you do here is set up the view1 path as shown above, but then when views asks you about parent item, you should select "normal menu item" and give it a title.
Now what will happen is, at the path "myview" Views will display the view "myview/view1" because it's the default tab's data. Effectively, the path "myview/view1" becomes the path "myview". Sort of.
I have tried to recreate your setup using Views 2 (as I had tabbed stuff to hand already) but could not get a Page as a "root item" with tabbed views as children... :( I think this is the limitation (perhaps of Views, perhaps of the Menu system).
Hope that helps.
Comment #4
domesticat CreditAttribution: domesticat commentedClosed while closing all Views support requests with no activity for 6 months. If you still need help, you may re-open this issue at any time.