I’ve found a workaround/cheat for this.
You can create the form as usual, export it as json, modify the field keys in the json, save and import them 🙂
I’ve found a workaround/cheat for this.
You can create the form as usual, export it as json, modify the field keys in the json, save and import them 🙂
I have a similar problem, I’m loading fields using acf_form and manually specifying which fields I want by their name but when they load in the page, I still see their original id and name:
<input id=”acf-field_5644ca0ecae0b” class=”” type=”text” placeholder=”” value=”” name=”acf[field_5644ca0ecae0b]”>
How could I have them loaded with the name I assigned ?
Thanks!
I had to delete all the “new_” fields from wp_options but they keep getting generated (for select fields). Do you know what is causing this ?
After hours of debugging, I came across this post. I was having some select fields preloaded (only select fields and some of them). Turns out, I had the new_ fields in my wp_options table.
Why and how do they generate ? how can I prevent this from happening again ?
Thanks
Hey guys, just bought a 5.2.3 license and “Show this field group if” is still broken for pages, when trying to match equal to. Not equal to seems to be working, but it’s not what I want.
Any help over here ?
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.