I'm not sure is this issue related to #594992: Incompatability with CCK fieldsets and multigroups. I'm also not sure which module is responsable of this but please feel free to correct issue information.

I have created an group to simplify node edit form. I have three CCK fields under this group. By going to group's configuration and changing group style setting, I wan't to make sure it is a seperated fieldgroup between title and few of CCK fields. Instead, it gets attached into vertical tabs.

I have tried all style settings resulting no change of behavior.

Am I missing something or is this a bug?

Comments

lolmaus’s picture

Subscribing. 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?

Grayside’s picture

Thirded.

hnln’s picture

subscribe

bsuttis’s picture

Confirming issue

bsuttis’s picture

Visiting /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.

lolmaus’s picture

> #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.

etomilin’s picture

subscribe

> 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.

spgd01’s picture

Subscribe

j0rd’s picture

Second 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.

enzipher’s picture

Version: 6.x-1.0-rc1 » 6.x-1.0-rc2
Component: User interface » Code
Status: Active » Needs review
StatusFileSize
new623 bytes

Hey,

The attached patch fixed the issue for me, although not thoroughly tested.

It looks like the issue is caused by #group not being set and as such gets the defaults.

Cheers,

osopolar’s picture

Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

Finally this got reviewed ;)

imiksu’s picture

LOL, it took almost 4 years, oh those times :)

osopolar’s picture

And maybe 4 more years to get it in cck ;)

imiksu’s picture

Maybe now?

jcnventura’s picture

Considering 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