Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I think the category fieldset should be collapsed by default if there are any required containers within it.
I have found that my users don't see (or know) about the collapsed area, so the top ones get selected every time.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | category_always_uncollapse_cats.patch.txt | 821 bytes | Bèr Kessels |
Comments
Comment #1
Bèr Kessels commentedAttached is a small patch which always uncollapses the fieldset in the nodes. Hardcoded collapsed by default is bad usability.
Ideally the (un)collapsed state would be a setting for each container.
Comment #2
inforeto commented+1 to this, plus bump.
I don't know about making it per container, but i'd certainly like it per content_type.
Looks like a task for a new cck related sub-module, by reading the fieldset settings from a cck field group.
It'd only take the option to assign the field group in the content_type settings, the widget to print $form['category'] in that field group and the piece of code to hide/disable the generic category fieldset.
Comment #3
JirkaRybka commentedIt's not only just uncollapsing the fieldset - if the selection is Required, it should not default to any value. Submitting a node without explicit category-selection done by the user, that should result in error-message asking the user to choose a category.
I've created this bigger patch, and submitted here: http://drupal.org/node/122285
Marking this as duplicate, because the small patch is already included in my bigger one, and both the Issues are basically about the same thing.