@tpeleg No, sorry, didn’t manage to find a solution. Below is the response I got to the support ticket I submitted… I replied (on 28th Oct) clarifying that I hadn’t even gotten to the point of saving to the database and haven’t had a response…
James Stout replied
Thanks a lot for the mail,
ACF uses the field’s name (see field settings) to save a value into the database. When saving sub fields, the ‘save name’ is generated by the ancestors names + the row index and can become quite long. It is possible that the length of this ‘save name’ can become too long for the wp_options table, and WP will not be able to save the value at all.
Kindly try creating a duplicate filed for use inside the layout and let me know if the problem persists.
Hope to hear from you soon.
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!