Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was testing the pay-as-you-go automatic translations option and encountered two issues: (1) an unexpectedly high number of translation credits were used, and (2) the content of the translated page was not visible when trying to review it.
Solution:
For the first issue, it was clarified that metadata attached to the page was also translated, which increased the word count and thus the credits used. To prevent this, the client can add the following line to their wp-config.php file:

define( 'ACFML_EXCLUDE_FIELD_GROUP_STRINGS_IN_POST_JOBS', true );

For the second issue, the fields on the page needed to be set to 'Translate' to appear in the translation editor. The client was advised to update the ACF field settings according to the guides on translating sites built with ACF, available here:
Setting Field Group Translation Option
Expert Translation Option

If these solutions do not resolve your issues or seem outdated, we recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, feel free to contact us directly at the WPML support forum.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 17 replies, has 3 voices.

Last updated by rikkeL 1 year, 7 months ago.

Assisted by: Prosenjit Barman.

Author Posts
May 15, 2024 at 7:58 am #15628110

rikkeL

We've now created a video that shows the issue: hidden link

May 16, 2024 at 3:07 am #15632633

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hi Rikke,
Thank you for sharing the video and further explaining the issue.

As I already mentioned, if the translation preference for any field is set to "Copy Once," the default data from English will be copied to the translation during automatic translation. Only fields with the translation preference set to "Translate" will appear in the translation editor. In the video, I noticed that only the "field_description," "title," and Yoast SEO information appeared in the translation editor because their translation preferences are set to "Translate."

In simple terms, you can use automatic translation with "Copy Once." However, automatic translation will only translate fields set to "Translate." If the translation preference for a field is set to "Copy Once," the default content will be copied to the translation.

I hope you can understand. However, if you need further clarification or assistance, please feel free to let me know. I will discuss this matter with the 2nd tier team and advice you on what to do next.

Best regards,
Prosenjit

May 16, 2024 at 7:16 am #15633167

rikkeL

Hi again

Thank you for clarifying.

This could have been a bit easier, if you had just answered our initial questions:

Can we use automatic translation with Copy Once: no

Will we need to change the settings of all our 282 pages of fields: yes

Best,
Rikke