Thanks for testing. I just merged it.
With ver. 2.0.0 there seem to be a problem with the autofill functionality of Caldera Forms. Expected behaviour: Defining an input field in the a form processor as an option group allows you to choose this option field in Caldera Form as a source for autofill for an dropdown field, a checkbox field or a radiobutton field. Using the form this fields would then be autopopulated with the options of the option group within CiviCRM. Current behaviour: Defining an input field as an option group in the form processor, you can still select this input in Caldera Forms. When the form is then loaded, no options are shown. Maybe a duplicate with #67 first point?
kainuk (53550239) at 28 Mar 15:52
This is a fix for #68
Thanks!
The modules recommended for Drupal 7 now all also support Drupal 10.
This solves the problem I found. Thanks a lot for the PR!
Thanks for your feedback @jaapjansma !
Its indeed a mess. There is one repo for cmrf_core containing different releases for D7 and D10. And there is two different repos for cmrf_form_processor, one for D7 and a different one for D10.
I did a correcting commit.
@RoWo-DS are you sure? I believe the mmodules for drupal 10 have different names and are in fact different modules. Probably better to only rename the heading of Drupal 8 to Drupal 9 and Drupal 10.
The modules recommended for Drupal 7 now all also support Drupal 10.
Hi @simon.hermann, I had the same problem and I created a fix for it. It is now in !73 (merged). Can you test it?
This is a fix for #68
This is a fix for issue #68 (closed)
kainuk (53550239) at 14 Mar 17:13
This call used to able to filter on name, this fix brings that back
Thanks, @JonGold . Tested it and it is solved...
jaapjansma (ddfef3ff) at 20 Feb 10:33
2.0.6-dev
jaapjansma (3bd0b06e) at 20 Feb 10:33
2.0.5
jaapjansma (3bd0b06e) at 20 Feb 10:32
2.0.5