Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Something weird going on...
I have 51 fields created. 50 states using term reference to the respective cities, plus one "State" field using term reference with all the states. So, you would click on "State" and select a state (Ohio for example), then I use conditional field to make visible OHIO cities in a drop down. This all works perfectly when I have "State" field settings > "Number of values" set to "1". The problem is when I set "Number of values" to anything higher than "1" then when my users go to their /edit page ALL 51 fields are visible. UNTIL they select any state from the "State" field. Then ALL the fields (except for the state they selected) immediately go invisible..the way it should look from the start.
I'm not using any other "field" modules. So, nothing should be conflicting with it.
My CF settings are: Condition: Value > Values input mode: All these values (AND)... > Set of values: whatever the term values is > Interaction...: XOR. Everything else is default. I've made myself dizzy trying many setting combinations, but nothing change the fact that all my fields are visible.
This obviously has something to do with the "Number of values" set to >=2. I'm hoping that there is some off the wall setting combination that I haven't tried.
Please help! I'm loosing my marbles.
PS...Yes, my users must have the ability to select up to 5 states and up to 20 cites from those states. As a side not, if anyone has a better way of making that happen I would really love to know. My html page size is over 1M. Load time is crazy! But, since I'm only developing the proof of concept I can life with it for now.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | InAction.PNG | 8.74 KB | System Lord |
| #7 | manage_dependencies.PNG | 54.97 KB | System Lord |
| conditionalFields.JPG | 33.79 KB | System Lord |
Comments
Comment #1
System Lord CreditAttribution: System Lord commentedComment #2
tahiticlic CreditAttribution: tahiticlic commentedSame problem here.
Comment #3
System Lord CreditAttribution: System Lord commentedtahiticlic,
For what its worth /project/field-conditional-state works perfectly for me.
Comment #4
tahiticlic CreditAttribution: tahiticlic commentedGreat! Thanks a lot, I didn't find this one, I'll give this module a try
Comment #5
System Lord CreditAttribution: System Lord commentedHmm, may have an issue with FCS. May not work when fields have combined field type: term reference and list (text). FCS is acting like its been hit by a truck. All my settings seem to have the opposite effect.
Comment #6
System Lord CreditAttribution: System Lord commentedI would still like to have someone address my lead post.
Comment #7
System Lord CreditAttribution: System Lord commentedI got this to work but it isn't ideal. I had to create a dummy field or placeholder so that I could establish an additional dependency. See "manage_dependencies." With "Alabama" depending on two conditions now I'm able to hide all 56 (according to BHO) states. The field "Number of states" has no use, other than being an anchor, and is hidden from display.
If anyone has figured out how I need to do this the right way, please let me know.
Comment #8
dqdThanks for the reports and all the efforts in here. But due to inactivity in this issue for years and because of the upcoming EOL of Drupal 7, I will close this issue on th way cleaning up the issue queue.
Feel free to re-open as "Needs review" if you found a solution or have a patch to be reported to help others.