- Issue created by @jmoreira
- last update
about 2 years ago 130 pass - last update
almost 2 years ago 130 pass - 🇧🇪Belgium nonom Brussels
I was debugging #3 because wasn't working for me. It seems the value to fill was in e.effect.options.fill instead e.effect.fill.
Once replaced the e.effect.fill references by e.effect.options.fill it worked.
Thanks, patch attached.
- 🇺🇸United States jmester13
I tried this patch with moderation state and found it does not address that functionality.
Example:
Boolean is required when Moderation State is In Review.
Following for suggestions and ideas.
- Assigned to jigish.addweb
- last update
almost 2 years ago 130 pass - last update
about 1 year ago 130 pass - 🇺🇸United States sethfisher
Here's a new version of the patch which fixes an issue I found. If you edit an existing node with a pre-existing value in the target field, choosing the triggering value will set the target field to the pre-existing value rather than the value that's supposed to be triggered.
- 🇮🇹Italy cicciobat Italy
Hi, I have a select list that controls two other field when a option is matched, whit this patch the first of the two field is shown but the second one none, in console this error is shown:
Uncaught ReferenceError: effect is not defined
at line 115 of conditional_fields.js.
If I try to print out the effect variable, actually is undefined, have any idea? - 🇮🇹Italy cicciobat Italy
I have attached a possible patch, let me know if it works and is okay.
- 🇮🇹Italy cicciobat Italy
Please, ignore the previous one since it was made from a project root, this one shuld works. Thanks.