I’m not sure how to describe this, but here it goes.
When trying to add a new custom field on a page/post, on the drop down I get the CF key instead of the name, but this only happens for the most recent CF I’ve created, as you can see on the screen shot, the first ones look fine ( ingredients, content etc..).
I had the exact same problem. I was getting ACF names like “field_5229dbec8dec1” and I couldn’t figure out how to get the proper names to appear even though that field had been named “food” and dummy data had been added to every custom field and published (so Elliot’s answer above is incorrect).
It took a while, but I realised that any custom field that I had named with any letter after ‘f’ was being replaced by the default meta key name.
So… I renamed every “custom field name” (not the label) with a prefix of “a-“.
I was now able to import my custom fields as intended, albeit with an ‘a-‘ prefix.
I hope this helps as a workaround for anyone with similar problems.
Viewing 5 posts - 1 through 5 (of 5 total)
The topic ‘meta key instead of name on add new custom field, instead of name’ is closed to new replies.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Last week, we released ACF 5.10 🎉 This update includes the brand new HTML escaping feature, which helps to keep your ACF-generated content safe. Learn about this and other new goodies in the release post: https://t.co/p9gKUYmdDQ