Hello!
Thanks for the feedback. This is not a bug, it is just how ACF save data. It is currently not possible to save a sub field value without saving it’s parent, that’s why you have to check all the parent field if you want to save it. If I would allow it, then ACF wouldn’t be able to correctly construct the meta data and retrieve it after that.
You’ll have to rework your field group data structure if you want to isolate some specific acf data.
The case is different for the loading method, where you can load specific sub field value, without necessarily having to load it’s parent. That’s why it is allowed in the “Load” tab.
Hope it helps!
Regards.
Thanks @hwk-fr
I tried saving the parent “group” field too, but it doesn’t save the child entries annoyingly! (they still don’t appear as an option to check either).
However the fields within the “column” type save perfectly well without (parent column) being checked.
If the group won’t work, i guess i can try the column field type.
Thanks
I have managed to use Columns to group together a few fields, i can see they are saving as i can see the values here:
In the CMS -> CPT -> Post #1234
But if i try to load a ACFe form (update) into a page, all the fields (in Columns) show correctly apart from the repeater field.
– Column 6/6
— field 1 (text)
— Field 2 (repeater)
—— Date picker (this repeats)
– Column Endpoint
The repeater field consists of a date picker and for my test i added two date fields on the form, then when i come to view this ACFe form (with update action) The number of Date picker fields is correct, but the entries are blank…
It can clearly see there are two date entries in the ACFe update form, but there are no values, but when you view the post in CMS as a CPT post, the values are visible.
Any ideas?
Thanks
Hello,
Sorry for the late answer, I’m still quite busy with the latest update. I received a ticket support earlier about loading values that doesn’t work in repeater/groups. In fact, there is a problem if you check the sub-fields in the “Fields Values” checkboxes.
Here is the ticket: https://ww.wp.xz.cn/support/topic/front-end-from-2/#post-12522333
So yeah, for “Field Values” you got to only check the parent (just like for saving), and not the childs. Screenshot: https://i.imgur.com/DqvFI9y.png
After doing that it will correctly load all sub fields values of the repeater/group, and not just rows without values (which trick you to believe saving doesn’t work, when it actually does).
The upcoming update will remove sub-fields in the “Field Values” checkboxes, just like the saving checkboxes. In the future, I’ll probably find a better UI than “checkboxes” to manage that stuff, but for now, that’s the best solution.
The update will also come with some nice UI improvements for Dynamic Forms. I think you gonna like it!
Sorry for the inconvenience.
Regards.
Thank you @hwk-fr that now works!
RE: update – sounds great! looking forward to it. It won’t change anything i have already setup will it?
Hello,
It will work out of the box for everyone. That’s why the update take that much time to come out, because I have to upgrade old form configurations, importer tool etc… 🙂
Regards.
