Switch for Category field groups to be collapsed or not
guidot - February 1, 2009 - 21:57
| Project: | Taxonomy Super Select |
| Version: | 6.x-1.0 |
| Component: | User interface |
| Category: | feature request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | reviewed & tested by the community |
Description
Thank you for writing this helpful module!
It would be nice to have an option that allows the administrator to decide whether or not category field groups are collapsed. It would also help if they stay open when the category is marked as required (as they are in the 5.x-version).
#1
I think so too
#2
I had the same need on two sites so I implemented it. A patch for DRUPAL-6--1 branch is included.
#3
Any news if this is going to get included in the module? I already have multiple sites using a patched version of module and it would be nice to know what is going to happen. Thanks.
#4
+1 for this, I have multiple taxonomy selector checkboxes for nodes, and it's a real hassle to have them all be collapsed, thankfully this is on a dev site because my users would never unexpand 5 different fields to get to the taxonomy selector. Is there any update when this can be integrated into the stable or dev release?
Please let me know...
Thanks!
P.S. What's the effectiveness of the patch? Has anyone tested it?
#5
(I'm marking this as critical as I see this as an extremely important feature)
The patch seemed a little out of date (it broke my module). However, the code behind it works extremely well. I tested the settings and it works exactly as expected. Best of all, rolling it out into a release will not require any database updates.
+1
Attached are new patches
#6
thx kmonty i just patched taxonomy_super_select-module-367659-2.patch to a copysite on my testserver and it works perfectly! and for people who don't know about patching i attached the patched module! hope it helps somebody ;-)
P.S. just copy in /sites/all/modules and look in taxonomy for new options.
#7
Great. Thanks. Just dropped in the new version. Site was in development, so I didn't even have to disable the module since it was a code change. Everything seems to be working fine.