If Conditional fields aren't using the role based configuration, it still takes up a fairly large chunk of the export feature definition (a lot of num => 0's). My proposal is to clean it up at the source, on insert/update of the values.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 2027307-5.patch | 1.7 KB | joelpittet |
| #5 | interdiff.txt | 541 bytes | joelpittet |
Comments
Comment #1
finex commentedHi, the function added with the patch has been named "conditiona_fields_clean_up_options", shouldn't be "conditional_fields_clean_up_options" instead?
Comment #2
hefox commented...yes, lol. typos!
Comment #3
hefox commentedComment #4
socialnicheguru commentedthis seems to work
Comment #5
joelpittetThis works great to clean up my export. Thanks @hefox.
I changed one thing, the
conditional_fields_dependency_updatehook wasn't doing anything because it wasn't passing in options to work on.Otherwise it worked perfectly. Sorry for the self RTBC, reset if you want a 3rd pair of eyes on it.
Comment #6
capysara commentedWorked for me!
Patch installed cleanly on 7.x-3.0-alpha2. I resaved the dependency and generated the feature and the extra => 0 were removed.
Thanks!
Comment #7
dqdApply/Test/Review ...
Comment #8
dqdWorks on latest 7.x dev.
Comment #10
dqdThanks for the report and all the hard work in here, very much appreciated.
Reviewed and tested and committed to latest 7.x dev. Hope it still helps someone out there! But please consider updating Drupal to latest core since EOL of Drupal 7 is coming soon.