Discovered this today. I’m trying to figure out how to have repeaters in the BuddyPress profile: https://github.com/locomo/acf-field-buddypress-groups
Not sure if it’s a solution. Still learning.
Thanks John I think converting over to those will do it.
Hi I just like to add that updating to 5.5.10 broke already established repeater fields. I reverted back to 5.4.3 and the issue resolved.
The code:
if(have_rows('body_sections')) :
while(have_rows('body_sections')) : the_row();
switch(get_sub_field('acf_fc_layout')) :
In 5.5.10 caused get_sub_field(‘acf_fc_layout’) to be blank. I did not have time to try and debug. I did run the db upgrade routine and resaved the ACF content to see if it fixed it.
Discovered why our issue is happening. It’s because we call register_field_group() on the backend but not the frontend so the acf-field cpt entry is not detected.
in /api/api-field.php in the _acf_get_field_by_key() method it users a get_posts query that looks for the custom field, but it’s not added in.
So get_rows for repeater fields depends on the custom fields being in the db, where as get_field() does not.
Here is a another summary if the first writeup is difficult to understand:
Basically what I need is a way to change the name input of a custom field depending on the post that is being edited.
So if we are editing a post that has a URL like this:
http://inboundsoon.dev/wp-admin/post.php?post=95897&action=edit&variation=2Then I need to modify the ACF saved name input to have -2 on the end of it.
And when the same page loads it needs to detect that it needs to populate custom field values from the values stored with -2 in the name key.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.