ACF Forms fields not populating after 0.9 update

Hello,

Thanks for the feedback!

Looking at the your JSON file, you try to load ACF Fields values from the “Current Post” (where the form is display). Which means ACF Fields need to be displayed and have some values on the Admin Page that display the shortcode in your WP Admin.

I ran a test using similar setup, and it works fine on my end. Here is a video on my test.

Are you sure your fields are displayed, with values, on the the admin page that display the form shortcode, like in my video?

Maybe you had a different configuration and you meant to retrieve field values from another post. Since your other forms work correctly, you can try to check them out, maybe you’ll find your custom configuration in there.

Hope it helps!

Regards.

I appreciate the video, but I can’t find a solution based on that. Nothing with my forms has changed in months – everything was working perfectly until the update today.

My form shortcode is inserted on a separate page but pulls in the CPT post ID [acfe_form ID=”123″ post_id=’CPT post_id’]. Here’s an example of the URL: https://mysite.com/my-page/post_id=12345. The shortcode is not inserted on the CPT pages where these ACF fields belong.

Should I have this configured differently now after the update? Something has changed – any ideas? Thanks.

Oh okay I see.

In fact, you should never override the post_id argument of the form. This is an internal argument that is used at several locations in the form logic, and might have undesired effect.

Instead you should pass a custom argument, for example target_id , so your shortcode would look like:

[acfe_form ID="123" target_id="456"]

Then use that argument in your Post Action UI: Target/Source settings with the template tag: {form:target_id} .

Here is a video showing this logic in action.

You’ll find a guide explaining how to pass custom data and retrieve them in the Form UI here. In this guide we use a custom profile_id argument, but it’s the same logic.

PS: The new 0.9.0.1 patch is up and fix the migration issue when using Auto Update. Sorry for the inconvenience.

Hope it helps!

Have a nice day!

Regards.

Yes, that helps, thank you. I have made some progress. However, another issue I’m working through.

3 of the 6 fields in my custom HTML do not populate. And, yes, I have verified the field names using {render:acf_field_name}, and the checkboxes are checked in the “load” tab. If I allow the form to generate the HTML, all fields populate.

Any ideas?

Thank you – I appreciate the help.

Hello,

Well it’s hard to tell. You have to provide more information, screenshots and details, otherwise I can only answer with more questions.

What are these fields? What are their field types? How are they different from the one that are correctly filled?

I would recommend to try to use field key instead of field name in the tag {render:field_abcdef}. ACF can be capricious if there are multiple fields with the same “name” in all your Field Groups. It will just retrieve the first one it finds, and it might not be the good one that is supposed to be filled.

Other than that, please keep in mind you can only render top level fields. You cannot just render a Group sub field or a Repeater sub field, it must be the whole Group or the whole Repeater. This is a core ACF limitation.

Hope it helps!

Regards.