ACFML 1.1 allows you to set the translation preferences of custom fields from within the field group page.

This feature has been requested by many of our clients who use the Advanced Custom Fileds plugin on their WPML multilingual sites. In previous versions of ACFML, you had to set the translation preference for each custom filed from the Multilingual Content Setup box when editing a post or from the Custom Field Translation section on the WPML Settings page. Now, with ACFML 1.1, you can easily set the translation preference for any custom field from within the field group page.

Setting custom fields translation preferences from the field group editing page

Setting the custom fields translation preference

Now you can easily set the custom fields translation preference when creating the field group from the Translation Preferences section.

Reviewing the translation preference after updating to ACFML 1.1

Reviewing the translation preference of custom fields after updating to ACFML 1.1

Setting the custom fields translation preference from the Field Group screen is introduced in ACFML version 1.1. If you have set the translation preference for your custom field(s) using an older version of ACFML, you will see a red tooltip icon next to that field. It indicates that the translation preference of that fields needs to be reviewed. Otherwise, the default value (Don’t translate) will be set.

Please make sure to review the translation preference of the fields that require revision before updating the field group.

Translating ACF Fields

Translating ACF fields

Whether you using WPML’s Advanced Translation Editor or the Classic Translation Editor, you will be able to translate ACF custom field values when translating your post or a page.

Download and Install

ACFML download on the WPML account page

You can find the Advanced Custom Fields Multilingual plugin on the downloads page of your WPML account.

Feedback

How do you like the improved translation workflow for Advanced Custom Fields? Let us know in the comments.

6 Responses to “ACFML 1.1 with improved workflow for setting the translation preferences of custom fields”

  1. I never understood all the issues and glue plugins for ACF and WPML… When I develop a multilingual site with custom fields, it just works out of the box. Even option pages, etc.
    Maybe someone can explain why this is necessary?

    • Hi Daniel,

      Thanks for reaching out!

      To be able to translate custom fields, you need to set them as “translatable” in WPML. The ACFML glue plugin facilitates setting the translation preference for custom fields built using the ACF plugin.

      For more details, check out our guide which explains the process of translating sites built with ACF.

    • In older versions of ACFML, you were able to set the translation preferences for custom fields from:
      1- The Multilingual Content Setup box when editing a post
      2- The WPML Settings page, under the Custom Field Translation section.

      Now, with ACFML 1.1, you can set the translation preference from within the field group editing screen. This comes really handy if you are creating a new field group as you will be able to set the translation preference of the custom fields when creating it.

  2. Hola,

    He diseñado una web con Elemntor pro y Crocoblock, este último tiene la posibilidad de crear Custom Post Type, Plantillas de productos simples y Archivos de dichos productos. Mi pregunta es si se puede traducir esto (CPT, Single products y Archive productos).

    Gracias de antemano.

Leave a Reply

Please leave here comments about this page only.
For technical support and feature suggestions, head to our forum. We are waiting there!

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>