We have some pages made up of reusable blocks made with ACF fields that we want to translate. Some fields need to be copy and others copy once, and we have set the ACF fields appropriately as described on https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/#translating-fields-in-wordpress-editor. We also need to use the default WP editor because we are going to be importing translations. But every time that we attempt to translate the page we only get a blank WP editor with no blocks. We do have the option to copy in the content from the English version and it does this correctly, but the fields that we would like to be copy are completely editable and not syncing with the English version. Is there a way to get the ACF field translation settings to work for blocks?
Thanks for contacting WPML forums support. I'll be glad to help you today.
First of all, sorry for the late reply due to a higher workload. I would need a site snapshot if possible.
We usually recommend the free Plugin “Duplicator” for this porpoise.
If you already know how Duplicator works. (http://wordpress.org/plugins/duplicator/),
please skip the following steps and send me the installer file and the zipped package you downloaded.
★ Duplicator Instructions (hidden link)
Send me both files (you probably want to use DropBox, Google Drive, or similar services, as the snapshot file will be quite big)
I will enable your next answer as private, so you can provide me with the information securely.
We have a shell site with testing data and fewer plugins where we have reproduced this issue. If you will let me post another private message, I can now provide a Duplicator backup of this shell site.
As you said in your response, you changed the field group translation mode to "Same fields across languages" from "Expert". This causes all fields to be set for translation, which is what we do not want. As stated in the original question, "some fields need to be set to copy and others set to copy once".
The client wants some fields to not be translatable and instead sync when they are changed in the original English version of the page. "Same fields across languages" does not allow for this.
The correct translation settings were assigned to the fields in the provided package. For example, on the Content tab the Title, Copy, Link Label, and Link URL are copy once and Video URL, Multiple CTAs, and CTAs are copy.
As was stated originally "We do have the option to copy in the content from the English version and it does this correctly, but the fields that we would like to be copy are completely editable and not syncing with the English version." Your example video does not show the fields that are set to "copy".
In other places, the fields that were set to copy often have a lock icon next to them and are sometimes even disabled. None of the reusable block fields either show the lock icon nor are they disabled. Additionally, we can edit the French version of these fields separately from the English version of these fields.
This is not what we want to do. We want the fields set to "copy" to only be editable in the English version of the page, and the French value to sync with the English value. This is how fields set to "copy" work in other places, and is how the setting of "copy" is described in the WPML documentation.
Osama will be away for a few days, so I will take over your ticket. I hope this is ok with you.
I tried the same steps with another field group for posts and it works as expected. The fields set to "Copy" are synced across languages and can be edited only from the default language as you can see here: hidden link
That behavior with copy does work in other places as you have noted, as we have seen it working on ACF fields assigned directly to a post object. We would like it working that way on reusable blocks as well.
The "Expert Option" section of the "Translating ACF Blocks With WPML" documentation page (https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-acf-blocks-with-wpml/#acf-blocks-expert) simply links to the same Expert translation option page that was linked to in the original question and also worked for setting up the translation settings on the ACF fields assigned directly to post objects, leading us to believe that the translation settings would also be correctly applied to the reusable blocks.
The similar ticket that you linked is over 2 years old and so is not visible to us.
It might be a bit different from the case you have as in the old ticket the values were not copied, but it describes why the translation preferences of the fields inside ACF blocks behave in a different way from the ones assigned directly to posts/pages.
I'm still waiting for a reply from our developers to confirm if this is still the expected behavior or if we have a workaround to make it work for blocks. I will update you here soon.
This is not the answer that we were hoping for, but we understand. You may want to update your documentation, as this situation is not only undocumented but implied to be working differently.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
