I have a futher question: is it possible to provide in the backend a possibility to have a second field for a translation on demand? Lets say, i have some fields with text and for this certain fields i have a button that says something like “need to translate” and by clicking this button a field will be created (named like the original field plus prefix/suffix).
Or is it better (for performance / databse…) to decide width fields should or could be translate and to provide a second field for all this fields.
Or is it better to work with a conditional logic, to provide a second field?
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!