Posted by RumpledElf on October 29, 2011 at 12:14am
32 followers
Jump to:
| Project: | Conditional Fields |
| Version: | 7.x-3.x-dev |
| Component: | Compatibility w/ other modules |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Conditional fields doesn't work when your conditional field is a HS one - I know HS is kind of buggy but it would be lovely to have the functionality in d7 at some point.
Meanwhile it works without using the HS widget but now I'm inflicting a very large and heavily nested select list on my users :(
My usecase is a shopping type site where I want to show things like size and colour only in the clothing section of a reasonably large list of categories that also include electronics, gardening etc.
Comments
#1
Subscribing
#2
Actually scratch this request - have written a new module that *does* have perfect compatibility with conditional fields - it was written with CF in mind.
Really need to get this new module either onto d.o as its own project or somehow get it as a fork/new version of HS. Wish me luck. Its a lovely multi-level taxonomy select widget/form element that has a different UI but same functionality as the HS taxonomy select widget. PM me if you're desperate for this functionality, I'll email you a copy.
#3
Glad you were able to create a solution. But, please don't 'scratch' your request. It is a much needed feature since HS (although buggy) has a respectable number of installs and, is more flexible than the core select list. It seems logical that modules that create or manipulate fields but, provide different functionality in D7 would all be compatible with each other. I'm just getting my feet wet with Drupal but, from all that I've read, the change to entities and making everything fieldable provides greater opportunities and flexibility. So, it seems reasonable that CF and HS somehow close the incompatibility gap.
I'm not a coder but, I want to get up to speed so that I can help with issues such as this.
#4
Hi, I am facing the same problem with conditional fields and Hierarchical Select working together. I will be glad if you can email me a copy or give me a link to access you new wonderful module
#5
Hi,
I have to face the same issue for my website.I am also interested in your module giraffian.
thx
#6
HS compatibility would be nice. It also has the same issues with Term Reference Select. This would save me from having multiple content types and vocabs.
#7
Subscribing
#8
Willing to sponsor the addition of this feature. E-mail me at antonio@bsidestudios.com if interested
#9
Conditional fields module doesn't work with Hierarchical select module
is there patch ?
#10
I have the same problem with the HS and CF D7 someone can help me please, or if possible an idea of how to do the same functionality of HS with another module, and if it is compatible with CF
thanks
#11
Actually I found CF to work with HS but you must enter numeric value of the dependee. For Example if you want to display the field only when term "example 1" is selected you should check what is the numeric value of that field in the database ...lets say the value is 7.... That's all you need to enter an it worked for me
#12
I can not understand, and I tested having a field of taxonomy Select control normal core and field dependence of I works perfect. reviewing the option value assigned to hand a value in the field dependence of this works perfect for defcto select control, but over this field HS (Hieralchical Select) and does not work, can you guide me or tell me as you did for you work, you do not understand what you mean by the value of the database ... That table is talking about? because for example in my case ... the term of the taxonomy I'm using is the second level, and the id of the term is "63" the same value appears in the option value select Default control. and HS also appears in the second level, but does dependency.
You can help me or explain to me how it was run please. I carry a lot of time trying to solve it and still can not get
thanks
#13
@mackpipe1
I am afraid I am having trouble understanding you mate. For me it worked exactly as described above
#14
@Mario Baron
I'm eager to try your solution, but I'm curious which version of Conditional Fields you are using because the rest of us over here: http://drupal.org/node/1542706 can't get Conditional Fields to work at all (in the sense of hiding / showing fields & the data actually saving).
If you are using an unaltered 7.x-3.x-dev, do you by chance know which commit date yours is?
#15
@Mario Baron
Well, using the direct input method (e.g. "All these values" / "Any of these values") does make my other conditional fields work properly: show/hide and data being saved, but it still isn't working with HS.
#16
Same here.
Please make CF compatibility for HS
#17
Hi,
I just want to know if someday this issue will have any avhievements on a near / far future?
Thanks
#18
Same here. Subscribing.
#19
Would be a nice feature, but certainly this is not a critical bug.
I would postpone the issue since Hierarchical Select for Drupal 7 is still in alpha... But I don't want to discourage anyone willing to work on the integration, which I would happily review.
#20
Hi all,
I have the same problem!And I have found a solution that works nice for me, i tell it if someone can be useful.
Using this module: https://github.com/juliquiron/drupal-sync_taxo_fields I replicated the taxonomy field and configured the module and conditions, also installed the Trem reference tree (http://drupal.org/project/term_reference_tree).
The result is nice taxonomy selection effect (Term reference tree) and the conditional working. Its not a compatibility with HS and does not use AJAX but works nice and solved my problem.
I hope can be useful for someone.
#21
Another good workaround is to use the Taxonomy Container module combined with the Chosen module--this approach will give you a nice autocomplete combined with a grouped select list that looks really nice, plus it will work with Conditional fields since it's just a select element.
Taxonomy container groupings only go one level deep, however, but it should be relatively straightforward to add support to the module for more complex taxonomies, since all the module does is replace the parent taxonomy terms with an optgroup element.