We are sending a page for translations to our vendor. The delivered file is not being read and translated correctly. Fields marked as translatable are not being detected, and HTML fields that are marked as not translatable are being detected.
Is there any documentation that you are following?
Yes, our developers have looked through online WPML documentation.
Is there a similar example that we can see?
In the .xliff file, we can see HTML being picked up for <source> when it should not be. In other instances, text that should be picked up for translation is not being detected at all.
What is the link to your site?
Example page where this issue is occuring during our test: hidden link
I understand the issue you're experiencing. If the translation preference is set to 'Not Translatable,' the field data should not be included in the XLIFF file. Only the field set to 'Translatable' should be included in the XLIFF.
While checking the WPML debug info, I noticed that the ACF Multilingual, WPML, and String Translation plugins are not updated to their latest versions. Specifically, the version of the ACF Multilingual plugin installed on your site is quite old.
Please update the ACF Multilingual, WPML, and String Translation plugins to their latest versions (ACF Multilingual → 2.1.3, WPML → 4.6.10, String Translation → 3.2.12).
After updating, change the field group setting to 'Expert' and set the translation preference for the fields you want to include in the XLIFF file to 'Translate'. Once done, make a small change in the page or post to apply the changes. Then try to create the XLIFF file again.
Hi, in the past 2 days we have made sure to try out everything before getting back to this question. We have now update the plugins to the following versions:
What we expect to happen is that the fields inside this block appear as they are configured. Meaning: If the field has wpml_cf_preferences: 1, it should not appear in the translation export or the editor because it is marked as "Copy" and we want the fields that are set as wpml_cf_preferences: 2 to appear in the translations. For some fields this works and we can change their translation status, but some other fields, regardless of what we set as the configuration, do not appear in the translation or cannot be disabled in the translation. Example of a field that we are currently testing is the field "field_64132aa6c4b56" above in the JSON. We have these configurations in our staging environment, but the field does not appear in the editor. We will attach the translation editor screenshot.
Hello There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
Thank you for providing more details about the issue. I see that the translation preference for certain fields is set to 2, which means they are translatable. Therefore, the field data should appear in the translation editor. However, could you please share the translation option set for the field group under which these fields are located?
You can navigate to "ACF → Field Groups," open the field group, and at the top, you'll see a banner to set the translation option for the field group.
If it's set to anything other than 'Expert,' please switch to the 'Expert' option and then check again. The ACF fields can only be set to translatable with the "Expert" option selected.
Please let me know the update. I will be happy to help if you need further assistance in this matter.
Thank you very much for the help. If you pay close attention in the JSONs you will see that both ACFs have `"acfml_field_group_mode": "advanced"`. Shouldn't this mean that the expert button was clicked?
We have tried clicking the button directly in the dashboard on our local development machines. But we have not clicked any buttons in the staging environment. Instead, we have just uploaded the ACF JSONs to staging. (We are versioning the ACF files as JSONs they cannot be found in the database, because we don't sync them once we upload them. They are purely saved in the ACFs.) We would also like to keep it that way if possible.
I understand your requirements. If the key acfml_field_group_mode is included in the JSON, the translation mode for the field group should adjust accordingly. However, instead of setting the mode to 'advanced' in the JSON file, could you please set it to translation and check if this changes the result? You may need to make a small change in the default contents and then recreate the XLIFF file.
You also mentioned that in the local development environment, you changed the translation mode for the field group from the ACF Dashboard. Could you let me know if that made any difference in the result?
Please let me know the update. I will be happy to help if you need further assistance in this matter.
Hi There,
Thank you for trying out the suggestions.
As the issue persists, I kindly request you try replicating the issue in our sandbox environment. This will help us easily isolate the problem in this minimal setup. In this way, we can also easily escalate the issue to our developers if required. The autologin link to our sandbox is provided below.
- hidden link
WPML and its add-ons are already installed in the sandbox. Please install ACF and any other plugins needed to recreate the issue. Set up the plugins as they are on your site and try to replicate the issue. If you need to access the files(to store ACF JSON files), you can use the "File Manager" plugin installed in the sandbox.
Please let me know if you're able to replicate the issue in the sandbox. I will take a closer look and be happy to assist you further.
Thank you for your kind cooperation in this matter.
Best regards,
Prosenjit
The topic ‘[Closed] ACF settings are not being picked up correctly in .xliff file’ is closed to new replies.
