Chainalysis
Tell us what you are trying to do?
If we upgrade to ACFML 2.x, how can we opt-out of field label translations and field choice translations?
Is there any documentation that you are following?https://wpml.org/compatibility/2023/03/acfml-2-0-easy-multilingual-setup-and-translation/
Is there a similar example that we can see?https://wpml.org/compatibility/2023/03/acfml-2-0-easy-multilingual-setup-and-translation/
What is the link to your site?hidden link
Andreas W. Supporter
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Timezone:
America/Lima (GMT-05:00)
Hello,
The new ACFML Translation Mode is pre-configured and is dedicated to clients, that want a preset setup and no need for customizing translation preference settings.
The only way to control all fields is by switching to Legacy Mode (Expert).
Best regards
Chainalysis
Hi Andreas, how may I switch to Legacy mode and opt out of the label translations?
When I search for "ACFML legacy" on wpml.org, I don't find any relevant documentation.
https://wpml.org//?s=acfml+legacy
alexC-33
I'm having the same problem from updating from 1.10.4 to 2.0.2.
Whenever I translate a page now, I'm presented with all the admin field labels and instructions etc. I only want the translation screen to present the field values .
Is there a quick and easy way this functionality can be disabled, otherwise I'm going to have to downgrade back to 1.10.4.
Andreas W. Supporter
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Timezone:
America/Lima (GMT-05:00)
Hello,
On ACF you can determine how each Field Group should be translated on Custom Fields > Field Groups:
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#using-the-acf-multilingual-setup
The Legacy Mode should be called Expert mode now - it is the only mode that lets you configure the fields on your own, the same as it was before ACFML 2.0.
Documentations:https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/
I hope this helps, if not, please let me know.
Best regards
alexC-33
From what I can see, I have to update all my ACF fields to tell WPML not to translate the 'admin text' (labels/instructions etc) ?
I've got a *lot* of fields, so it'll take absolutely ages for me to update them all. Is there no other way to do this?
Chainalysis
Andreas, thank you for the info but I think that I'm not understanding a key step here.
These are the three links you shared:
1. https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#using-the-acf-multilingual-setup
This page explains how to translate field labels, and explain the option to translate via the ATE or string translations.
But it does not seem to include instructions that enable me to opt out of label translation completely.
2. https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/expert-translation-option/
This page seems to indicate that if a field is set to be Translatable, then the labels will be translatable.
It does not seem to explain how to opt out of label translations, while still being able to translate field values.
3. https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/recommended-custom-fields-translation-preferences-for-acf-and-wpml/
This page doesn't seem to mention the word "label" at all, so I'm not sure how this might help me to opt out of label translation.
...
To be clear, I would like to continue to translate field values but I would like to opt out of translating field labels .
The ACF field labels are not relevant to our translation work, which we perform almost exclusively in the ATE.
being forced to translate ACF field labels will add complexity and increase the price of automated translations, while adding no value to us.
So this is why we would like to opt out of this label translation feature, please.
Andreas W. Supporter
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Timezone:
America/Lima (GMT-05:00)
Hello,
ACFML has a new mode called "Same Fields across languages":
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#selecting-a-translation-option
If you use this mode, then labels will be included in the WPML Translation Editor.
If you use the mode "Different fields across languages", then the labels should not show up on the WPML Translation Editor but can optionally be translated on WPML String Translation.
Also, you can use the Expert mode, which is the same Legacy Mode, that ACFML used to use in the past, without any predefined settings from our side.
I hope this clarified the issue, but if not, or if you experience some unexpected issues, then please let me know.
Also, take note, that if you change the settings while you still have open jobs in the translation queue, you will need to complete "In progress" translation jobs first in order to see new settings applied in the next translation job for this content.
Best regards
alexC-33
All my field groups are set to 'Expert'. This was what they were set to by default after updating.
Even though they are 'Expert', I still see the field labels showing up when translating.
When I try changing a field group to 'Different fields across languages', I get the following notice when trying to update a translation:
"You need to translate this post manually because the field groups attached to it use different translation options."
No matter what I try, the labels always seem to show up.
With every test I perform I am making sure to avoid any "In Progress" jobs, as I know this will preserve fields even if I change settings.
Chainalysis
Hi Andreas, I'm bumping this ticket because I wasn't able to work on this yesterday or today, and I don't want the ticket to close automatically.
Will be in touch on Monday, thank you.
Andreas W. Supporter
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Timezone:
America/Lima (GMT-05:00)
Hello,
Please take note that we have published a workaround that allows excluding label translations from the WPML Translation Editor:
https://wpml.org/errata/advanced-custom-fields-multilingual-the-group-fields-title-and-labels-are-translatable-by-default/
Anyhow, please take note, that according to the design of the new ACFML labels should get translated this way, if you use "Same fields across languages".
Best regards
Chainalysis
Thank you, Andreas. I'll give this a try on a test environment, and will report back.
Andreas W. Supporter
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Timezone:
America/Lima (GMT-05:00)
Hello,
Thank you, please let me know if further assistance is needed.
Best regards
Chainalysis
Hi Andreas, I've re-upgraded to ACFML 2.x and commented out that line as you instructed.
I also deleted all of the existing acf-* string translations such as the "acf-field-group-4661" domain.
However, within WPML > Translation Management, I still see dozens of ACF Field Group translations available, such as "Field Group Labels 4661".
How can I remove these labels from the list?
Andreas W. Supporter
Languages:
English (English )
Spanish (Español )
German (Deutsch )
Timezone:
America/Lima (GMT-05:00)
Hello,
You can go to WPML > String Translation, filter by text domains and delete the strings from there.
Or we could take a closer to the DB and use some mySQL queries on the table icl_strings and icl_string_translations?
Best regards
