The correct constant is
Prefixing is not really maintainable because I don’t know which languages our client will add… And can become a mess.
Creating a “global variables page” is what I was doing before using ACF Options… So I’d rather not regress 😛
For now I think I will replace “translatable” fields in the Options page by Repeaters ones, in which the key will be the language code.
It’s a shame that it’s not better handled, is it on your roadmap to enhance this Elliot ? It’s really a pleasure to work on complex and multilingual sites with ACF and WPML, except this part 😉
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!