Resolved

Resolved in: 3.5.3.1

Symptoms

The issue happens when using the Repeater field option in ACF Pro along with WPML, where the Repeater field’s parent field is set to be copied to the translated post.

As a result, the translated post's Repeater subfields are not displayed correctly – no matter how many repeater subfields you add to the translated post, the admin lists as many subfields as the original language post has.

For example, when you create a post in your default language and add four fields in the Repeater field, then translate this to the secondary language, you will not be able to add more than four fields in the repeater field of the secondary language.

Workaround

  1. Navigate to your translated post from your WordPress dashboard.
  2. Scroll down to the Multilingual content setup section.
  3. Find the ID of your repeater field and set its translation option to Don't translate.
  4. Click the Apply button.

acf-multilingual-content-setup-dont-translate

Note that you might not be able to choose the Don't translate option for a specific custom field (radio buttons are disabled) as it is set to Copy.

In this case, follow the below steps:

    1. In your WordPress dashboard navigate to WPML -> Translation Management -> click the Multilingual Content Setup tab and scroll down to the Custom Field Translation section.
    2. Find that specific field and change the option from copy from original to translation to Don't translate and click on the Save button

set-field-to-dont-translate

  1. On your WordPress dashboard navigate to Plugins -> Installed Plugins and Deactivate the WPML Translation Management plugin.
  2. Go to the post that you want to translate and edit/add your translated content to the repeater custom field.
  3. Navigate to the Plugins page and Activate the WPML Translation Management plugin.

8 תגובות אל “ACF – Issue with modifying the number of Repeater subfields for the translated posts”

  1. good afternoon, yesterday bought your plugin and started to perform the translation and I found two problems.

    1. When I load a new entry in another language, the picture is not me and I get an error when I want to put it in a container entries:
    http://sanswell.com/sin-titulo-1.jpg

    2. started translating the products of WooCommerce WooCommerce Multilingual and will bind the + sign and I load a blank page:
    http://sanswell.com/sin-titulo-2.jpg

    I can advise?

    Thank!!

  2. Hi,

    We've been having a lot of problems recently related to this issue. We are about to introduce a new language – our original plan was to use the Translation Management plugin to duplicate all the pages from an existing language first, then make any necessary modifications. However with the custom fields set to "Don't translate", none of the content in the custom fields is copied over.

    Do you know if it is safe to now downgrade to an older version of the plugin without this issue before doing the mass-duplication?

    Kind regards,
    Tomer Peleg

  3. Dear WPML Team,

    Is there any update on when this issue will be addressed. We have a site scheduled to go live and need to generate 200 pages in a new language (the site already has 10 other languages). The proposed workaround of disabling Translation Management and manually actioning each page individually does not really work for us with this many pages.

    Can you please advise if we can either:

    a) Downgrade safely to an earlier version of Translation Management.

    or

    b) Propose a suitable workaround (even if this requires a manual code change by us) pending an official fix.

    Many thanks,

    Julian

    • Hi Julian,

      We are in the process of closing a quick fix version of Core, String Translation, and Translation Management and scheduling the release by Monday given all tests pass.

      In Translation Management, we have removed the ACF compatibility class which was handling repeated fields and causing the issue.

      We will move this logic into the ACFML bridge plugin which will be also updated and released on the same day.

      Downgrading might not be the best option, as it would require downgrading all the plugins, but it shouldn't cause any issue if you prefer this option.
      However, I strongly recommend testing the downgrade before doing it in production.