Thanks, that helped me track it down. I think my problem was two-fold: I was using acf/update_field/name={field_name}
, where it should have been acf/update_value/name={field_name}
, and also, as you described, the key was required instead of the name for this repeater field. Thanks much!
Before WordPress 4.4, the group title would only display if you had “Style” set to “Metabox.” Now it displays for both “Seamless” and “Metabox”
So I kind of simplified how I’m displaying these on the front end. In actuality, it’s displaying in three select fields, with each taxonomy in it’s own field, and then some jQuery to show and hide different fields based on the user’s selection of Make.
Honestly I did think about doing it that way, but I didn’t want me client to be able to set up levels deeper than needed (for example, if I made it hierarchical, they could set up Honda > Civic > Accord > Fit > Element, and just keep going down).
Maybe I’ll just switch to hierarchical if this can’t be easily done; I can always just warn my client that making deeper levels of makes/models could break things.
Does this apply to ACF standard? I’m having issues with fields not saving as well.
This is only happening on pages with the “Page” post type. No idea why.
Same thing this morning, but mine aren’t just sub-fields, any custom fields on any page except the home page won’t save, and I can’t figure out why.
I concur! Right now I’m looking in to using the File field, but a native Video field would be excellent!
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 Privacy Policy. If you continue to use this site, you consent to our use of cookies.