Skip Navigation
Home » Errata » Advanced Custom Fields Multilingual - The Group Fields Title and Labels are translatable by default

Advanced Custom Fields Multilingual - The Group Fields Title and Labels are translatable by default

Resolved

Reported for: Advanced Custom Fields Multilingual 2.0.2

Resolved in: 2.0.4

Overview of the issue

With Advanced Custom Fields Multilingual 2.0.0 you will notice that the Group Fields Title and Labels are now translatable by default. It is not a bug, but a new feature included with our latest release. The idea is to translate these labels easily and affordably with the Advanced Translation Editor and its automatic translation feature.

You can find more information about it in our documentation.

Workaround

If you prefer not to have this feature, since Advanced Custom Fields Multilingual 2.0.4, you can disable it by defining this constant in your WordPress wp-config.php file:

define( 'ACFML_EXCLUDE_FIELD_GROUP_STRINGS_IN_POST_JOBS', true );

Note that if you have pending translation jobs with these extra strings, you will need to cancel it and re-create new jobs.

15 Responses to “Advanced Custom Fields Multilingual - The Group Fields Title and Labels are translatable by default”

  1. I updated yesterday all the acfml and wpml plugins and now i have all the website with Group Fields Title and Labels display on the translations…. I honestly not gonna think to use Wpml again.

    I used for years but the new versions are always full of problems…

    Reply

    • Hello Giorgio,
      I understand your feeling, however it is not a bug but a new feature. I’ll add a note in our devs ticket with your opinion.
      Anyway, does the workaround helped in your case?
      Thank you for your understanding.

      Reply

  2. Hi Andrés,
    The trick didn’t work and i restore a back up.

    I was a bit emotional because imagine you have a wordpress multisite with 6 languages and data-entry done for 8 subsite, almost ready, you update the plugin and find that you need to go on each page and translate every Group title or label otherwise the translations are not completed.

    The client wouldn’t be happy to lose more time and also in my opinion modifying a class in the plugin is not very maintainable.

    Anyways i worked with WPML for years and with the previous version I didn’t have big issues, so I’m a bit sad that on the latest versions there so much more complexity that is not really needed in my opinion or at least put a clear way to deactivate things you don’t need.

    For example why the automatic translations manager is not a plugin like media translation. If i dont use third party automatic translators i dont really need it. Its just add confusion and sometimes it’s hard to translate non textual elements.

    Feel free to ask anything, happy to help!

    Reply

    • Thanks again for your feedback Giorgio. However, if the workaround doesn’t help, feel free to open a chat in our support, in that way one of our specialists will check your case.
      Regards

      Reply

  3. This workaround seems to work, but I hope that the WPML team comes up with a more stable solution that allows customers to disable this feature that doesn’t require us to directly edit plugin code that will be overwritten when the plugin is updated.

    Reply

  4. Thanks for this workaround! Works for me. But please allow us to enable or disable this feature without manually editing the plugin. Before applying this workaround, my translation editor screens were cluttered with field labels and choices that I don’t want to be translatable.

    Reply

    • We are glad it worked! There is a new ACFML 2.0.4 available which allows you to set a constant to deactivate this new feature.
      We have updated the errata accordingly. 🙂

      Reply

  6. Hi

    We are in a very similar position to Giorgio. A page should be passed on for translation by a third party and suddenly the translation jobs are spammed with field labels and field instructions. But we don’t even need a translation of that.

    Please add an option as soon as possible to exclude field labels and instructions so that only the field content is passed to the translation editor. Your development team should know that this workaround is not sustainable at all.

    Reply