That’s actually pretty cool I wasn’t aware of the JS API.
I figured I’d need to do some AJAX to get the functionality I wanted so I started writing up a little script. I used your suggestion from another post to check out some examples from Hube2’s Github Link
While I got the base AJAX functionality going, this JS API might be a better/easier way to catch the events.
Thank you!
For now just to get it done, this is what I ended up doing:
When I take the Repeater out of the Flexible Content and attach it it directly to the page everything works!
Can you expand a little on the first part?
I don’t think the second option will work, because all the information is needed. I’ve attached a screenshot.
Yeah, unfortunatlly it is number one 🙁
Whats the saying? When the door is closed, climb through the window
I guess I’ll have to find another way unless anyone else has some fancy ideas.
Hi. Thanks for the help. It does indeed know the post id. Removing the section out of the flex content makes it work. The code you posted also shows the correct post id.
However, after a little more digging I seem to have found the issue.
It seems to be a known limitation: https://www.advancedcustomfields.com/resources/clone/#limitations
Any suggestions on getting around this?
For now I’m thinking of changing the clone inside the flex field to just duplicate the data.
Okay after further testing I have a little more info. I guess it has to do with the structure of my fields!
Currently the select field is part of Repeater, that is inside a Flexible Content.
When I take the Repeater out of the Flexible Content and attach it it directly to the page everything works!
I can’t seem to find the connection. I’ve tried adding Prefix Field Labels/Names but couldn’t get to work. The documentation states that clone fields are fields themself, but maybe I’m missing something.
I’m hoping this insight might be enough information to help us find a solution.
Screenshot-2....png
