That’s pretty hard to use when you’re defining whole field groups in a single array though.
This is why it has to be optional. I’d see it as an option on the field group :
'auto_keys' => true
Of course, it could break if you’re not careful. But it wouldn’t break on its own. It would only break if you do something silly like name two field groups, or two fields in the same field group, the exact same. Which is just a bad idea in the first place in most cases. Also, ACF could warn you: “These fields have the same key. We put a number so it should be fine for now, but watch out if…”
But the worst that can happen is that you lose your data and it gets saved under a new key from that moment forward… which always could happen with ACF if you decided to rename a field anyway.
Also it could be overwritable. If I know this field in particular is possibly going to have the same key as this other field, I could set their keys manually.
Back with an other question haha.
What do I do if my group field’s slug has an underscore in it ?
I mean, I could just change it to make it “my-group-field” instead of “my_group_field”, but it is in your system that when I write a field’s name with spaces, it replaces them with underscores, so that’s a shame.
Thank you very much for your help. It works just fine now.
Thank you very much! I didn’t manage to get it to work properly, so since I don’t have all that many terms, I just fetched them all and put an if statement to control which ones were displayed. But interesting to know that it’s somehow possible.
Same here, I roll-back to previous version, thanks to back up 😉
