Skip Navigation
Home » WPML Blog – News and Updates for the WordPress Multilingual Plugin » Compatibility » ACF Multilingual 2.0 – One-Step Multilingual Setup and Easy Field Label Translation

ACF Multilingual 2.0 – One-Step Multilingual Setup and Easy Field Label Translation

Compatibility
14

Today, we released ACF Multilingual 2.0. This version comes with a new and improved workflow that makes translating custom fields intuitive and simple. 

Update: ACFML 2.0.5 is now available

After releasing ACFML 2.0, we got very useful feedback from clients which allowed us to quickly fix some minor, but important issues. The latest version of ACFML is now 2.0.5 and for the best experience, we strongly recommend running that version on your multilingual, ACF-powered sites.

With this release of ACF Multilingual (ACFML), we made it our mission to simplify and streamline the custom field translation workflow. This is thanks to you, our ACF Multilingual users.

You let us know that the process of translating custom fields and field groups could be confusing – but it shouldn’t have to be. So, we went in and revamped the ACF Multilingual translation options and interface. 

These improvements elevate the usability of ACF Multilingual to a whole new level. See for yourself:

Read on for more about the top features and find the rest in the changelog.

Pre-Set Translation Options

With the new Multilingual Setup, you can configure the translation preferences for custom fields in just one step. 

You can choose between two pre-set translation options for each of your field groups: 

  • Same fields across languages – In this mode, you can use the same custom fields across languages. Then, use automatic translation or WPML’s Advanced Translation Editor to conveniently translate field labels and content.
  • Different fields across languages – This mode is for field groups that need to have different field configurations across different languages. In this mode, you translate your post and field content in the native WordPress editor.

For both of these options, ACF Multilingual automatically sets the translation preferences for the fields inside the field group for you.

Select a translation option with pre-set translation preferences for each field group

If you want to continue manually setting the translation preferences for each individual field, you can choose the Expert option. 

Have an existing site with field groups? We don’t want to change the translation preferences that work for you. Your existing field groups will use the Expert option and keep their existing options. But, you can choose the pre-set translation options for both existing and new fields you create!

Better Field Label Translation Workflow

In ACF Multilingual 2.0, translating field labels and labels for Choices is much simpler. You no longer need to go into your theme’s files and adjust the code to make the labels translation-ready. And, you can stop worrying about making the Field Group post type translatable.

Now, you can easily translate field titles, field labels, and labels for Choices based on the translation option you select for your field group.

  • In Same fields across languages, you just need to send a post using the field group for translation. All the labels will be available for translation in the Advanced Translation Editor. 
  • In Different fields across languages, you can translate the labels simply by going to WPML → String Translation.

Translating field labels and labels for Choices in the Advanced Translation Editor

Translating field labels and labels for Choices in String Translation

User Interface (UI) Upgrades

We know that your sites have a lot of custom fields and field groups assigned to different post types. Keeping track of what you need to do to translate your content, and where you need to go to translate it, isn’t always easy.

The improvements to the ACF Multilingual interface make it easier to navigate the custom field translation process. 

Each translation option comes with tips on where to go to translate your field labels. And if your custom fields are assigned to a custom post type that isn’t translatable, ACF Multilingual will let you know. 

See where you need to go to translate the field labels in each field group

Stay on top of the translation settings for post types attached to field groups

How to Install ACF Multilingual 2.0

We’re releasing ACF Multilingual 2.0 gradually, and you’ll see the update on your site when it becomes available to you.

 If you don’t want to wait, you can go to Plugins → Add New and click on the Commercial tab. Then, hit  the Check for updates button.

Feedback? Let Us Know

We hope you enjoy the new features and improvements in ACF Multilingual 2.0.

We would love to hear your feedback about this milestone release. Let us know if it improves your experience in translating ACF fields.

And of course, we’d love to hear any further feedback or questions. Leave us a comment below and our team will respond to all your questions and suggestions!

14 Responses to “ACF Multilingual 2.0 – One-Step Multilingual Setup and Easy Field Label Translation”

  1. I need this update now. My WordPress sites have been crippled since I can no longer use WPML and ACF for multilingual sites. I just wasted 3 days trying to find a work-around. I need this today! Can you send me the assets as I don’t see it available for download.

    Thank you.

    • Hello. As described in the post, you can easily get ACF Multilingual 2.0 in one of two ways:
      1. Log into WPML.org with your account and go to the Downloads page. Click the “Download WPML manually” link at the bottom of the page, scroll to “Advanced Custom Fields Multilingual” plugin, and click to download the plugin.
      2. On your site that is running an older version of ACF Multilingual, go to the Plugins page, click the “Add new” button at the top, and then click the “Commercial tab”. On the page that loads, click the “Check for updates” button and you will be able to update ACF Multilingual to version 2.0.

      If this doesn’t help and you’re still having issues, please feel free to ask for help in our Support Forum.

  2. Looks fantastic.

    Any issues for upgrading from previous versions?
    Other than full site backup any preparation you would recommend?

    Thanks again for the great work,
    Daveed

    • Hi, Daveed, thank you for your comment! On existing sites, all your existing ACF field groups will be set to use the “Expert” translation option. In other words, nothing will change and it will stay exactly the same as you had it set until now. So no, you shouldn’t see any issues. However, as you noted, doing a site backup is always recommended before upgrading any plugin to a new major version.

  3. Thank you; while improving the pulgin’s features is great, you should not forget to improve how fast it is (WPML slows sites down, compared to another wordpress translation solution); unfortunately I can’t use the other plugin, cuz it ll mean translate my whole site all over again.

    I am stuck with WPML 🙂 so please keep improving the speed aspect of your plugin

    • Hi! Can you please tell me if you raised these performance issues with our support? The best way for us to improve performance is by getting reports (forum tickets) from clients that experience any performance issues. That allows us to investigate the site, the server, and everything that might be causing it. So, if you have done this already, please share the tickets and we’ll take a look. If you haven’t yet raised this issue, please do so, and again, please share it here so that we can take a closer look. Thanks!

      That being said, yes, we are planning further performance improvements, but there generally shouldn’t be any big slowdowns coming from WPML at this point.

    • I’d like to add one more thing about ACF Multilingual 2.0 and its performance… Compared to the previous workflow consisting of duplicating the field group in the secondary languages (and changing the field labels in the translated version), we get 9% fewer database queries (from 98 down to 89) and load time is 22% faster when displaying a translated page on the front-end (no speed change on the page in the original language).

      In other words, our feature to translate field group labels does not add any extra database requests anymore now, and the new code to translate the labels causes no slowdown in the site either.

      • Hi Dario,

        thanks for your reply, No, I didn’t create any ticket.

        I actually just talked to your support, and The thing is I installed string translation and media translation even though I don’t really need them; Now, I only keep the core plugin (without media and string); I believe that will be great fro my site’s performance;

        Also, you’re right, the host’s server and other factors play a role in site’s speed;

        Still, I am glad that you working on the plugin performance.

        Keep up the good work 🙂

  4. Hi,
    Does it change anything for the integration with some builders? I just installed WPML on my WP site with Thrive theme and it creashed…
    Si was wondeting if you were supporting Thrive now or if the problem woulb still be there.
    Thank you
    Anouk

    • Hi Anouk.
      Unfortunately this release won’t change anything in relation to Thrive Themes compatibility. We reached their team numerous times in the past but we are still awaiting availability and cooperation from them before we can proceed with resolving compatibility with their themes and plugins. I would suggest that you contact them to help push this forward 🙂 In the meantime I will reach them again to see if they now have more capacity to work on this project.

  6. Hi, is it normal that local path is saved on json local file? We use it to sync projects’ custom fields between installations. Those files shouldn’t include such absolute local path.
    Thanks