- First commit to issue fork.
- πΊπΈUnited States weekbeforenext Asheville, NC
weekbeforenext β changed the visibility of the branch 3063335-support-for-entity to hidden.
- last update
11 months ago 130 pass - πΊπΈUnited States weekbeforenext Asheville, NC
The recent work requires the patch from #2856720 so I'm relating that issue.
- last update
11 months ago 130 pass - πΊπΈUnited States weekbeforenext Asheville, NC
I was able to build off the work in #2856720 and add conditions to handle entity_browser_forms. If you aren't referencing the 4.x-dev version, you'll need the patch from that issue.
Attached is a video comparing the conditional fields functionality of a standard inline entity form and one in an entity browser.
- last update
11 months ago 130 pass - πΊπΈUnited States weekbeforenext Asheville, NC
weekbeforenext β changed the visibility of the branch 3063335 to hidden.
- πΊπΈUnited States weekbeforenext Asheville, NC
weekbeforenext β changed the visibility of the branch conditional_fields-3063335-3063335-4 to hidden.
- πΊπΈUnited States weekbeforenext Asheville, NC
I resolved merge conflicts in the MR, but the functionality isn't working as expected on my site. I will be circling back to this.
- πΊπΈUnited States weekbeforenext Asheville, NC
This seems to be working for me again locally on 4.0.0-alpha6 if I apply the Drupal core patch from https://www.drupal.org/project/drupal/issues/3468860 π Form field #states not woring with entity reference fields Active and revert conditional_fields.js to the alpha5 version. The remaining issues with the javascript can be followed in this issue: https://www.drupal.org/project/conditional_fields/issues/3503448 π Interdependent field conditions not working: "Undefined" value set Active .