Posted by quicksketch on October 13, 2008 at 5:50am
Jump to:
| Project: | Vertical Tabs |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | quicksketch |
| Status: | closed (fixed) |
Issue Summary
This is an issue to discuss/monitor the concept of enabling certain fieldsets but not others on the node form. Personally, I think it'd make most sense (in both ease of implementation and flexibility) if the options to configure which fieldsets to enable were available by node-type. This means that the configuration would likely exist at admin/content/node-types/[node-type] in it's own fieldset.
Implementation-wise, this could loop through the existing node-edit form for the content type being configured, then display a list of all the fieldsets currently on the node form, allowing all Fieldsets to be enabled (such as the Taxonomy or CCK fieldsets).
Comments
#1
subscribe.
some themes are having trouble with the tabs
http://img261.imageshack.us/img261/5847/20081101032623en9.png
2 custom fields and input format is left out ! how can i add them or thats not possible at the moment?
#2
I would really like to see this feature, too!
#3
Also, could you add "taxonomy" as an optional fieldset. With a little css styling, taxonomy works well with this module.
#4
+1 for a configuration form
ps just saw // TODO: Make a settings page to turn on and off certain fieldsets. on the module file so it is in the TODO list already
#5
I just finished up these configuration options. By default all core fieldsets are put into Vertical Tabs, but the tabs for each type may be configured at admin/content/types/[type-name].
#6
Thumbs up!
#7
Automatically closed -- issue fixed for two weeks with no activity.
#8
Note: #503290: Vertical tabs fieldset configuration breaks horribly for multi-step node forms
#9
I would really like this feature back, I miss being able to choose my vertical tabs! :-)
#10
@jenlampton: Please read the http://drupal.org/project/vertical_tabs project page which points you to http://drupal.org/project/form which lets you do this (in a way that doesn't horribly break on multi-step node forms, even).
#11
@dww: I also read on http://drupal.org/project/form that "This code is pre-alpha quality" which makes me sad.
Could I suggest restoring the old behavior, but with the default setting to do nothing, therefore not breaking anything unless the admin does it on purpose?
#12
Also taken from the Form module page:
So, two bad things here...
a) Views breaks. Almost every site uses it.
b) Won't be solved until D7 means really looong time. Year(s) maybe?
That's why I think it should be solved in VT itself and I am setting this back to 'active'. Anyways, depending on other modules should be avoided where possible I think.
I've never used VT in a version that supported this feature like some people mention here, but if I get this straight there used to be some kind of checkbox in each new CCK field's settings to include/exclude it in VT. Am I right?
#13
This already has been implemented.
#14
Sorry Dave, I misread/mistook 'fieldsets' for 'fields'.
Is there a way to set this per CCK field? ...or do I need to add a separate fieldset that is not rendered in vt and put fields I need to exclude in it?
#15
Fieldsets are all our nothing in Vertical tabs. If you want some fields in, some field out you'll need two separate fieldsets.
#16
Automatically closed -- issue fixed for 2 weeks with no activity.
#17
Procedure to configure which fieldsets are rendered as vertical tabs: On admin/settings/vertical-tabs check "Expose vertical tabs selection on the edit content type forms" and then go to the settings of each content type where you have now an option for vertical tabs to select "Include the following elements in the vertical tabs" with checkboxes to enable or disable each tab.