Resolved

Resolved in: ACFML 1.3

Symptoms

With ACFML 1.2 we have ability to translate ACF Options Pages using String Translation Packages. Basically, if you create options page and provide some values, you should go to WPML String Translation screen and translate those values.

Unfortunately, it is not working well in every case. For time being we have spotted two issues.

Translating compound fields doesn’t work

For now you can translate this way only textual fields (inline text or textarea). If you are going to use more sophisticated fields, like for example URL field (which is compound of two values: URL and the anchor text), in the String Translation you will some encoded value, hardly possible to translate.

For compound fields please consider using a group of fields instead of them. For example, in case of the URL field, consider creating two fields: one textual field for the URL and one textual field for anchor text. Keep in mind this will require you to update your template files responsible for displaying those values.

Migration from old way of Options Pages translation doesn’t work

Before ACFML 1.2 it was possible to translate Options Pages’ values by switching language switcher on Options Page edit screen. This didn’t work at all for many users (so this is why we introduced a new method) but for some of you it did.

After updating to ACFML 1.2 your translated options pages will work fine with one except: if you go and update values, you will lose your translations. So if your options page values are final, you don’t have to worry about anything.

But if you want to update some value or provide a new one, consider one of two options:

  • provide a new value and translate all values again with a new interface
  • if this is not an option for you (for example you uses compound fields and/or you have too many values to translate them again), please, for the time of the update, downgrade ACFML to version 1.1, update Options Pages and after that, update ACFML to the newest version.

We are sorry for inconveniences and we will address both issues in one of the nearest future release but as long as this errata is published, please follow the instructions above.

Workaround