This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with translating content using an XLIFF file and the WPML built-in translation editor. After setting the ACF field to 'Translate' and resaving the page, the exported XLIFF file still shows the target content in the source language, and the WPML translation editor appears blank. Solution: First, ensure that all WPML and related plugins (such as ACF) are updated to the latest versions. After updating, you should edit the original content where the ACF field was changed, save it, and then attempt the translation again. It's important to translate from the original content into the second language using one consistent method, either all through WPML editors or all manually, but not a mix of both. If you previously used manual translation methods and wish to switch to using WPML editors, be aware that you will need to re-translate the content as WPML will not recognize manually added translations in the second language.
If this solution does not resolve your issue or seems outdated, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket at WPML support forum for further assistance.
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.
Background of the issue:
I am trying to perform a translation using an XLIFF file on the site hidden link. I've set the ACF field to Translate and resaved the page.
Symptoms:
When exporting an XLIFF file, the target content is in the source language. Additionally, when using the built-in translation editor in WPML, it's blank.
Questions:
Why is the target content in the XLIFF file in the source language?
Why is the built-in translation editor in WPML showing blank?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
Thank you for your message.
After making a change to an ACF field's setting you will currently need to edit the field on the original content and then save the content, to make the field available for translations.
The source language of your content can be different than the site's default language. The admin language that was set when creating the original post or pages, determines the source language of the original content.
An original content can be identified by the fact that inside the right sidebar of the WordPress Editor, you will see the options to see the translation method which can be "WPML Translation Editor" or "WordPress Editor".
You should always translate from original content into a second language. Only once the original content has been updated WPML will update the translation status and will expect that the translations need an update.
---
Can you please name me the title or permalink of the content that you are trying to translate and allow me access to your staging site?
I would like to request temporary access (wp-admin and FTP) to the site to investigate the issue further.
The required fields are below the comment section when you log in to leave the next reply. The information you provide is private, meaning only you and I can see and access it.
IMPORTANT
Please be sure to back up the site and database before granting us access.
If you can't see the "wp-admin / FTP" fields, your post and site login details will be set to "PUBLIC". DO NOT publish the data unless you see the required wp-admin / FTP fields.
The private reply form looks like this: hidden link
The next time you reply, click on "I still need assistance".
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We are not allowed to access any credentials that were not specifically submitted on this ticket in the private response form.
I have updated all my plugins to the latest version.
I have gone into the page in question and made updates and saved and then made a new translation request but the language in the target field is still in the primary language in the xliff file.
Is it possible to get the already translated langauge from the translated page into the target field or do I need to re translate it as it was just set to copy before?
I am not sure if you translated it before in another way or if some configuration was wrong. Maybe you added translation in 2nd language manually via WordPress editor, that would explain why WPML can not identify it.
Can you please try to re-translate the page as you do regulary ( Using XLIFF or WPML editor), you can do a test with a new test simple page and see if the issue still occurs? I think it should work fine then.
I stated in another chat with you that I the translations were done by copying the page to another language and then, using the wordpress backend editor added the translations.
Then when I asked if I could export xliff filed they told me to put the ACF fields to translate. When that didnt work I created this file.
Are you saying that since it was not translated using XLIFF files or the WPML editor that I can not export the secondary language and that in order to use XLIFF files instead of the wordpress editor I need to retranslate what is already translated?
Would I also be correct in saying that if I were to change my setup to use XLIFF files or the WPML editor instead, all my languages has to be translated this way, or is it possible to combine the different methods?
yes, that is correct, you can not combine different translation methods. Same way if you add now some changes in the default language and start using WPML editors, it will remove all manually added content in 2nd language and you need to add them again via WPML translation editor.
Thus, in general, you can not combine manual translation methods with WPML editors as you will need to re-translate, you need to use one translation method or if switching some things will require re-translation.
Note that also using the WPML Advanced Translation Editor for pages you already translated with the WPML Classic editor may cause issues, such as missing translations. To avoid problems, we recommend using the Advanced Translation Editor in general.
