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.Hi, when a dependent item launch 'state:disabled' event, chosen should be updated to get disabled too.
I made a patch may help.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | chosen-states-integration-8.x-2213635-5.patch | 896 bytes | sukanya.ramakrishnan |
| 0001-Integrate-with-states.js_.patch | 1.2 KB | capynet | |
Comments
Comment #1
Dave ReidDo we need to check
if (e.trigger) {like the code in states.js does?Comment #2
capynet CreditAttribution: capynet commentedActually is not necessary. states expose these events to avoid these kind of internal checks I think.
Comment #3
joelpittetI gave this patch a try with term_merge module to see if it would help and was no luck. It is initialized as disabled. And for some reason chosen doesn't un-disable when the state changes.
Comment #4
bitcookie CreditAttribution: bitcookie commentedThis patch works with the Conditional Fields module and enabled/disabled. Thanks!
Comment #5
sukanya.ramakrishnan CreditAttribution: sukanya.ramakrishnan commentedThanks, I needed a fix for this bug for 8.x, I am submitting a similar version of this patch(folder changed for js file) for 8.x here.
regards,
Sukanya
Comment #6
geertvd CreditAttribution: geertvd at XIO commentedPatch in #5 worked nicely for me, haven't tried it with term_merge as it is not ported yet.
Comment #8
nagy.balint CreditAttribution: nagy.balint commentedComment #9
markhalliwellThe 7.x patch for this is now included in #2859781-5: Optimize JavaScript.
The 8.x version of this has also been simplified in that same issue.
Comment #10
nagy.balint CreditAttribution: nagy.balint commented