Registration can’t fill field group

Hi @mukape

I hope you are doing well.

I am afraid the group field has some limitations including the Group mapping, our developers are already working on some improvements for this and we would like to include your case too, however, for this could you please export your form and ACF fields, upload on a Google drive and we can check how you configured the fields and the plugin?

To export the Form: https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#import-export

Best Regards
Patrick Freitas

hello dear, thanks for fast response
I’m trying to use Forminator for user registration in my website, the users should provide me with some details or fill profile. this profile includes personal info like name, nationality, age, educational info and experiences .. like a CV
educational and experiences fields should be a Field group because the applicant may have more than one entry in those two fields.
1st of all: I made this fields using ACF, then I created the registration form using Forminator and matched the custom fields between Forminator and ACF
It’s working well for all the fields, but when we come to field groups: it’s not filling the ACF fields like the other single fields.
here is the link for Google drive contains exported Forminator form and ACF fields
waiting for your results.
Regarding

Hi @mukape

Thank you for additional explanation and sharing the form/fields.

I checked it on my end and we are dealing with two things here:

1. Forminator’s field groups.

As my colleague already mentioned, it’s quite a new feature of Forminator and there are certain limitations. Currently, if such a repeater group field is mapped to any custom field (or used with any 3rd-party integration) only the data from the “first set of fields” will be passed over.

What that means is that if I only submit one set of “Education” fields in the form, that data will be mapped to custom fields. If I submit two or more sets of “Education” fields in the form, only data from the first set will be mapped to custom fields.

This is something our developers are working on and it will be improved with future releases (but I don’t have an ETA).

2. ACF repeater

The “Education” and “Expierience” ACF fields are ACF “repeater” fields. Those are specific fields and regardless of the issue stated above, there is no direct integration of Forminator and ACF in that sense that Forminator doesn’t provide data in any ACF-specific format. It only passes over “raw text” data to custom field.

If you check the DB that data is saved there (for the first “set” of grouped fields as explained in point 1) but ACF simply doesn’t know how to display it because it’s not in format expected by ACF.

This would require quite a big of custom code to be handled and such code would need to be custom developed. However, first the issue in Formiantor (point 1) would need to be addressed. It’s on a to do list for future but I don’t have ETA, I’m afraid.

Kind regards,
Adam

Hi,

Thank you for your valuable reply and quick response.

I know that you’ll fix it for me at least for now, and I know that also you’re working hard on developing Forminator, and I’m sure it’ll be a great plugin
If you can put integration with ACF on your plan, It’ll be a great point for Forminator, specially when Forminator is not only a form plugin, It’s doing a lot of main tasks and we can depend on.

Regarding to the field group, actually I don’t know how to fix this because I don’t have another way to fill users profile.

in your custom code, this values received via Forminator can pass into a variable to be converted into format that ACF can understand ?
in our scenario, if we’re talking about simple Forminator fields like name, input, number and so on, ACF can understand by the end.
can we convert the data passed in field group to be understood to ACF by the end like simple fields in custom code snippet ?

Actually, this plugin is great enough to do more the what it’s can do for now, you can plan to make integration with acf, cpt ui, sign up, login, creating profile and woocommerce.

Hi @mukape

Thanks for response!

The ACF compatibility is something that will be partially implemented indeed. I wouldn’t expect full support of all ACF formats out of the box anytime soon, I’m afraid, but we are working on certain improvements related to ACF support and that includes compatibility with repeater-type fields. So it’s gonna be there but I don’t really have any ETA yet.

if we’re talking about simple Forminator fields like name, input, number and so on, ACF can understand by the end.
can we convert the data passed in field group to be understood to ACF by the end like simple fields in custom code snippet ?

Yes, they are simple fields and if they weren’t a) group in Forminator and b) repeater in ACF – they would be “understandable to ACF”. The key point of the issue, however is the fact they are group/repeater and that’s the main problem here which requires changes/improvements in Formiantor code (as explained above). I’m afraid I don’t have any code snippet workaround for it and it wouldn’t be a simple solution – until it’s implemented in plugin’s code.

Kind regards,
Adam

Thanks for your valuable time.

I need to be notified when you fix it.

Regards

Hi @mukape

I hope you are doing well.

You can subscribe to our roadmap to receive notifications of upcoming improvements:https://wpmudev.com/roadmap/ but as Adam said we can’t give any ETA for this.

Best Regards
Patrick Freitas

Hello @mukape ,

We haven’t heard from you for over a week now, so it looks like you don’t have more questions for us.

Feel free to re-open this ticket if needed.

Kind regards
Kasia