Reviewed & tested by the community
Project:
Vertical Tabs
Version:
6.x-1.0-rc2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Aug 2010 at 08:30 UTC
Updated:
17 Nov 2020 at 15:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
lolmaus commentedSubscribing. I suffer from this issue too.
I create a fieldgroup and go to it's configuration. It's set to "always open", not "vertical tab".
But the fieldgroup is still getting transformed into a vertical tab! :(
How do i prevent that for a certain fieldgroup?
Comment #2
Grayside commentedThirded.
Comment #3
hnln commentedsubscribe
Comment #4
bsuttis commentedConfirming issue
Comment #5
bsuttis commentedVisiting /admin/settings/vertical-tabs and unchecking 'Include new fieldsets in vertical tabs by default' does the trick. If you check 'Expose vertical tabs selection on the edit content type forms' you'll also get a list on your content-type edit form where you can select which fieldsets appear as tabs.
Comment #6
lolmaus commented> #5 bsuttis
> Visiting /admin/settings/vertical-tabs and unchecking 'Include new fieldsets in vertical tabs by default' does the trick.
Okay, this might be a workaround but the issue still needs fixing.
Comment #7
etomilin commentedsubscribe
> Visiting /admin/settings/vertical-tabs and unchecking 'Include new fieldsets in vertical tabs by default' does the trick.
This option affects not only node edit forms, but also block forms and content type forms, excluding groups provided by additional modules form tabs.
Comment #8
spgd01 commentedSubscribe
Comment #9
j0rd commentedSecond this motion.
I'd like vertical tabs, added to most of my fieldsets by default, except for the cases when I don't. Thus checking to see if this option is set, then abiding by it would be a good solution.
Comment #10
enzipher commentedHey,
The attached patch fixed the issue for me, although not thoroughly tested.
It looks like the issue is caused by
#groupnot being set and as such gets the defaults.Cheers,
Comment #11
osopolarFinally this got reviewed ;)
Comment #12
imiksuLOL, it took almost 4 years, oh those times :)
Comment #13
osopolarAnd maybe 4 more years to get it in cck ;)
Comment #14
imiksuMaybe now?
Comment #15
jcnventuraConsidering that the last commit to this module was 9 years ago. And that this is for Drupal 6, which is no longer supported.. And that this module has no supported versions... I think the answer is no.
Hopefully, the answer would be to close all issues that are related to version 6.x-* of any module except maybe for https://www.drupal.org/project/d6lts