Background of the issue:
My site uses ACF blocks with field groups mapping to certain blocks in my theme. I've disabled translations for certain fields in the field group because they set class names or are used for other logic in my page templates. Additionally, I've tried disabling the block using a custom XML config and I'm still seeing it in the translation editor.
My video wouldn't upload so here is a Google Drive link: hidden link
Symptoms:
Despite disabling translations for certain fields, or disabling a block for translation altogether, they are still showing in the WPML translation editor.
Questions:
Why are fields that I've disabled for translation still appearing in the WPML translation editor?
How can I ensure that fields used for logic or class names are not translatable?
How can I disable certain ACF blocks from being translatable?
How can I disable certain fields for ACF blocks from being translatable?
Welcome to WPML support. I will answer this ticket before the ticket is assigned to one of my colleagues.
Would you please test by refreshing the page that contains the ACF fields?
- Go to your Dashboard > Pages.
- Open the edit screen of the original page. You should see a pencil/circle/gear icon in the sidebar options under the "Languages" section.
- Make a small change, for example, add an extra blank space at the end of a sentence/paragraph.
- Save it.
- You should now see that a circular arrow appears beside the 2nd languages links, this means that an update is required.
- Edit the translation again and save it up to 100% translated.
Also from what I understand you need some different layouts or fields for translated version. For that I suggest that you use the manual mode and different layout mode which is called localization. For more information:
This did not work. I'm still seeing the fields available for translation. Let's start with the first issue as it is my highest priority - I don't want certain ACF fields enabled for translation. These fields are being used with ACF blocks, and despite selecting "Don't Translate" on the ACF field, they are still showing in the translation editor.
I've attached another link to a video further explaining what I'm trying to accomplish. Please review and let me know how I can accomplish what I'm looking to do.
There are no individual fields inside of the group. The button group (docs: hidden link) takes in a list of options in the same way a dropdown does and then displays the options in a buttons format rather than a dropdown. I recorded a video explaining this further. Let me know if I'm missing something.
Additionally, this field that I'm using is just an example, but my issue is happening on all fields I'm trying to exclude from being translatable for my ACF blocks.
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Sorry for the misunderstanding.
This "Button Group" should be set to "copy" and its choices might appear on the WPML Translation if they have not yet been translated, but they further will be translatable with WPML > String Translation.
Once you make changes to a field or group in ACF you will always need to edit the respective field on the original content, save the page or post, and then open the WPML Translation Editor.
Does this solve the issue?
The exception here might be if those strings were already translated and are saved inside the translation memory of the Advanced Translation Editor and this seems to be the case in your example.
The topic ‘[Closed] Disabling ACF Block fields for translation’ is closed to new replies.
