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.Hopefully I'm filing this correctly and that it gets to someone. I installed this module in earnest expectation that the tabs that showed up would be IN-LIINE with the tabs that drupal normally produces. Instead I find myself viewing tabs that are WITHIN the "View" and "Edit" tabs that show up when you are an admin and looking at a post.
This is something really big here. Let me explain why. If you've ever used views you know that you can create tabbed views by just using cck and views. The way to do this is to create a view and assign each view that you want to show up as a tab the same "url" when you are "providing a page" -- hopefully those who are reading know what I mean. In any event, this is very time-consuming and really is not the most efficent way. Why? Here's why...
It would be PERFECT if when you installed this module you would get the following...
_| View | Overview | Order | Contact |_
Node content.
In this way the tabs replace the tabs that drupal normally creates. Get the picture? SO -- Instead of making a whole new section like this module does INSIDE my node, it will actually slice the node into tabs that can be CLICKED ON and it will act as a completely different page.
I am POSITIVE that there are many that want this functionality. For example I want to create a node -- ONE node, not 5 that will look like this...
(viewing "Overview" tab)
_| Overview | Download | Purchase |_
body_filter field
(viewing "Download" tab)
_| Overview | Download | Purchase |_
table list of file attachments
(viewing "Purchase" tab)
_| Overview | Download | Purchase |_
Instructions how to buy.
You see? Now you only have ONE node -- not 3, and you can view different sections of that node, without having any special setup. This als omakes scaling up easier.
Can this be done?
Comments
Comment #1
GreenLED CreditAttribution: GreenLED commented» Respectfully, GreenLED
»
Comment #2
nedjoI see the point. But the tabs Drupal produces by default are very different things from tabs as used here; they only happen to look the same. The View and Edit tabs are produced by the menu system as "local tasks" and are essentially links to other pages, not content that is available for display.
And, um, this is not a critical bug report.
Comment #3
GreenLED CreditAttribution: GreenLED commentedSo -- can this be implemented? Can those "LOCAL_TASKS" tabs be replaced or added to? Of course they "Edit" tab would not show up to guests -- unless you enabled the persmission. My point, it sounds like this could be done... you would have to create a module to do it though. I do not have the expertise yet. They way in which you speak in sounds like it can be done -- but it would not be in the "framework" of the build of the original api (oooooh, fancy language :). Yes, I am aware (not being sarcastic here) that this is not critical -- just wanted to get some attention to get it answered. Probably not the best policy.
An added note -- I really believe people are looking for this functionality, would this be something that would take a few months to put together?
» Respectfully, GreenLED
»
Comment #4
nedjoI think this is a duplicate of http://drupal.org/node/178607. Please read that issue. If it's not the same, you could reopen this one and explain.
Comment #5
GreenLED CreditAttribution: GreenLED commentedThis is not a duplicate. That issue is talking about moving all content that does not show up using "Tabs" (via jstools) to a separate tab. This request is talking about taking the tabs that "CCK Fieldgroup Tabs" creates and rendering them as"NORMAL" administration tabs that drupal usually uses.
Basically the tabs that are created by the module are totally unexpected. They need to be tabs that are apparently created by "LOCAL_TASK"
I'm really pushing this because this would cut-out even a lot of messing around with views when all you're trying to do is have ONE node with MULTIPLE tabs.
Basically what you're doing is sectioning off the page into "Fieldsets" by those "groups" will determine what goes in each tab. HOWEVER, THAT tab will be rendered as a "REAL" tab, not by jstools, but will show up jut like you would see this menu...
Goto: admin/content/types for example.
Content Types
_| List | Add content type | Fields |_
Got the idea?
So instead you would have a NODE like thus...
Some Exciting Title!
_| Overview | Details | Planning | Purchase Ticket |_
Your fieldgroups would thus be...
1. Overview
2. Details
3. Planning
4. Purchase Ticket
Under each of these would might have 2 or three cck fields.
Understood?
» Respectfully, GreenLED
»
Comment #6
nedjohttp://drupal.org/node/178607 has been implemented, addressing a similar feature request.