Closed (works as designed)
Project:
Vertical Tabs Default Tab
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Jul 2010 at 20:18 UTC
Updated:
18 Jul 2010 at 21:57 UTC
Hi.
It seems to me that vt_default breaks the normal (collapsible or collapsed) behavior of cck fieldgroups. If I enable vt_default it seems to turn all cck fieldgroups into vertical tabs, regardless of what I set in the fieldgroup settings (collapsible, collapsed, etc). I'm trying to find a way to make vt_default work with the insert module and solving this could be a way to make that work.
Any ideas?
Comments
Comment #1
crea commentedVT Default Tab only moves content that is not fieldset itself into default fieldset. What you observe is regular behavior of Vertical Tabs.
Comment #2
einkahumor commentedSorry, you're absolutely right. I think this should be a bug report though since there is a fieldgroup setting where you can select style ("always open", "collapsible", "collapsed" or "verical tab") but no matter how I set this, my groups are always rendered as Vertical Tabs. I've tested this using Garland with the latest stable release of Drupal, CCK and Vertical Tabs and also the latest dev of Vertical Tabs. Can anyone Shed some light on how to fix this? I'm no code ninja so any help would be greatly appreciated.
Comment #3
hefox commentedTry unchecking "Include new fieldsets in vertical tabs by default." at admin/settings/vertical-tabs ?
Comment #4
einkahumor commentedHeh. Well that works, thanks. Shouldn't this setting (when it is checked) make new fieldgroups have their style setting set to Vertical Tab instead of just overriding whatever is set?
Comment #5
hefox commentedfieldgroups is 'just' a add on module for CCK that adds fieldsets around cck fields.
Fieldsets are what this checkbox is for, not just specifically fieldgroups.
So to this option an non-something-else fieldgroup is a 'new/unconfigured' fieldset.
I believe vertical tabs can still be configured using form module, so I'd suggest using that to exclude fieldsets/fieldgroups. (I tend to just do it in code these days, but I'm weird).
Comment #6
einkahumor commentedThis issue has gone a full circle and is back to VT_Default. I've finally figured out that the real problem is that if I uncheck the "Include new fieldsets in vertical tabs by default." checkbox in admin/settings/vertical-tabs then I get no Default Tab behaviour. I can set the Default Tab title in admin/content/node-type/sometype but nothing happens until I recheck "Include new fieldsets in vertical tabs by default.". This is bad because I really need to use a collapsed fieldset within my Default Tab (for an imagefield with insert).
I think we can all agree that this isn't desirable behavior. I know almost nothing about php and javascript so I'm afraid I can't solve this on my own. Any ideas on how to fix this?
Comment #7
hefox commentedAs mentioned before, have you tried http://drupal.org/project/form to configure vertical tabs? (There is a conflict between form and views, but disable form after using it and the vertical tab settings keep).
In most of the sites I've used vertical tabs on, I've left the checkbox as is to no undesirable states, aka I don't agree.
Comment #8
einkahumor commentedI checked out Form when you mentioned it first but stopped reading at "This code has pre-alpha quality and we will rewrite it soon. Do not use on production sites." but I guess I could check it out. Thanks for pointing it out.
I just wanted to point out that VT_Default stops working if you uncheck "Include new fieldsets in vertical tabs by default." which I think is quite a flaw in the module.
Comment #9
crea commentedVT has a very long history of deciding what is a tab and what's not, so in the end VT Default Tab was left in a state where it assumes all fieldsets are tabs by default. There's hook mentioned on the project page, to control VT Default Tab behavior. You can change everything.
Comment #10
einkahumor commentedRogert that. Thanks.
Comment #11
einkahumor commentedSorry about the status change, didn't mean to do that.