Background of the issue:
I am trying to translate my blog posts automatically to Spanish using WPML.
Symptoms:
For some articles, only part of the content is being detected, so I'm unable to translate the full article automatically. WPML → Translation Management shows an incorrect word count, detecting only 8 or 200 words instead of the full 2,000. In the WPML editor, only the detected words appear for translation.
Questions:
Why is WPML not detecting the full content of my blog posts for translation?
How can I ensure that WPML detects all the words in my articles for automatic translation?
Please reply to this ticket if you need more help with this issue.
If you need further help with this, please share the access details to your site with me. I'm enabling a private message for the following reply. Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
Thank you for your reply. Itamar is not working today and he will be available on Sunday to work on this.
Meanwhile, I'd appreciate it if you could contact WP Engine and ask them to provide the copy of the website so if in any case Itamar needs tht it will be available for him on Sunday.
I checked and the link you provided works and the dashboard is accessible but as it is a live website there will be no way to deactivate or do some troubleshooting without breaking a live website.
Thanks for providing access to a staging site. I needed to create a new user to check the problem on the staging site because the temp user you gave me did not have an email address associated with it, and I could not add it. This made it impossible for me to translate content. I tried things in a minimal environment. I also duplicated the post with the problem and tried translating it from the duplication. Unfortunately, I could not solve this problem. I'm consulting our second-tier supporters about it. I'll update you here once I have their reply.
Our second-tier supporter instructed me to take a copy of your site and escalate this issue. I'm obligated to ask your permission to do that. Do you allow me to take a copy of your site? For this, I must install a plugin like Duplicator or All In One Migration. Please let me know if you agree.
The problem might be in the database. We need to conduct a deeper investigation to debug this issue, which we usually do on our servers. This is a standard workflow in such cases.
If you have sensitive data, such as users' details, that you don't want to expose to external sources (although we are not using it in any way), you can remove it from the staging site before we take a copy.
If you absolutely don't want us to take a copy of your site, I can ask our second-tier supporter if this issue can be debugged on the staging site.
Please let me know what you decide.
Please note that my weekend is Friday-Saturday, and I'll be able to continue to check this issue and help you on Sunday.
Our second-tier supporter told me that we already performed the tests we could on the staging site, which is why we asked for a copy of the site. However, if you are still reluctant to share a copy of your site, we can wait for other second-tier supporters to check this issue. Maybe they will find something on the staging site.
Our senior second-tier supporter reviewed the issue directly on your staging site. What they found is that the untranslated content (which appears in large portions) is **not missing from the database** — it’s stored correctly in the expected places, such as `wp_postmeta` and `_elementor_data`. However, **this content isn’t being included in the XLIFF file**, which is what the Advanced Translation Editor uses during translation.
They ran a test on a clean Elementor setup by copying and pasting the same content, and it was included in the XLIFF file as expected. This suggests that the issue is likely something **specific to your site's setup**.
To investigate further and determine exactly why the content is being skipped, we would need to take a copy of the site. We won’t proceed without your explicit permission, but this would greatly assist us in identifying the cause and finding a solution.
Please let us know how you’d like to proceed.
If you allow us to take a copy of your site, we must install a plugin such as Duplicator or All-in-One Migration. Please let me know if you agree.
We’ve decided not to move forward with copying the site. Instead, we’ll handle the translation manually or possibly skip those articles, as there aren’t many of them.
