Background of the issue:
We have manually translated all of the pages on the site into Spanish and French by uploading the XLIFF files. The site we need help with is hidden link.
Symptoms:
The pages are all saying they are translated, but once you switch to that language, the pages are still showing in English.
Questions:
Why are the translated pages still showing in English after uploading the XLIFF files?
Is there a specific step we might have missed in the translation process using WPML and Elementor?
Thank you for contacting WPML support, I’m happy to help you with this issue.
I see you are using the plugin GTranslate to translate the content on your site and I don't see the issue with WPML plugin. Can you please deactivate this plugin and use WPML to show the translation content? Also, please remove some configuration code generated by this plugin.
Refer to this ticket https://wpml.org/forums/topic/i-have-an-issue-with-the-language-switcher-3/
While checking the debug info, I see that the WordPress Memory Limit is below the requirements. The minimum requirements are 128M, but we do recommend 256M and the debug information of your site shows it set to 40M. Please check this link for more details https://wpml.org/home/minimum-requirements/.
I checked the htaccess file and I did not see that configuration code added by gTranslate. That plugin was only active because I can't get the WPML to work.
I also checked my site health and server configuration, it is showing my memory limit is set to 512M, so I don't know why it's saying 40M? I've attached a screenshot.
Please check out the spanish side and you can see nothing is being translated for the pages hidden link
I see the content isn't translated on the homepage. I suggest you follow steps below to re-translate the homepage and see if it helps:
1. Edit the homepage in English language.
2. Make a small change to the page title/content > Save.
3. Go to WPML > Translation Management > Send the homepage to translation.
4. Go to WPML > Translations > Export the XLIFF file and translate the content.
5. Re-import the new XLIFF file to your site.
If it still doesn't work, please share the new translated XLIFF file with me, I will help you check the issue.
I increased the WP Memory limit, but unfortunately it still doesn't work.
With your other suggestion, is it possible to enter those pages into the translation queue again but use the same XLIFF files? The reason is, a 3rd party translation service is doing them and we've already asked if they can re-do it once, we can't ask again. We had issues on the initial import. Is it possible to update something in the XLIFF files to get it to match the new translated page?
is it possible to enter those pages into the translation queue again but use the same XLIFF files?
Yes, it is possible. However, you need to ensure the old and new XLIFF files have the same structure. Then follow the documentation below to copy the ID of the new file to the old file and re-import the old file to your site. https://wpml.org/faq/the-uploaded-xliff-file-doesnt-belong-to-this-system/
If it doesn't help, please send the new XLIFF file to your translation service and ask them to re-translate the file.
You can upload the file to Google Drive or Dropbox ... then add the URL to your reply. Also, I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated. Your next reply is set to private to share the info.
I see the issue after checking the XLIFF files and the new one exported from your site:
1. The translation content in the XLIFF files that you received from the translation service does not have the correct format. The tag "<![CDATA[ ... ]]" is missing in the target tag which is translation content.
For example:
<trans-unit extradata="field-rank_math_description" resname="field-rank_math_description-0" restype="string" datatype="html" id="field-rank_math_description-0">
<source><![CDATA[Nictavi is an eye care product manufacturer and wholesaler deriving our forward-thinking innovations from a personal passion for preserving sight and reducing suffering.]]></source>
<target>Nictavi est un fabricant et grossiste de produits de soins oculaires qui tire ses innovations avant-gardistes d'une passion personnelle pour la préservation de la vue et la réduction de la souffrance.</target>
</trans-unit>
it should be:
<trans-unit extradata="field-rank_math_description" resname="field-rank_math_description-0" restype="string" datatype="html" id="field-rank_math_description-0">
<source><![CDATA[Nictavi is an eye care product manufacturer and wholesaler deriving our forward-thinking innovations from a personal passion for preserving sight and reducing suffering.]]></source>
<target><![CDATA[Nictavi est un fabricant et grossiste de produits de soins oculaires qui tire ses innovations avant-gardistes d'une passion personnelle pour la préservation de la vue et la réduction de la souffrance.]]></target>
</trans-unit>
2. The content structure is not the same, please check the attached screenshots.
I suggest you follow the steps above https://wpml.org/forums/topic/elementor-pages-arent-being-translated/#post-16000876
to make a small change to the page content and get new XLIFF files. Then send them to the translation service and ask them to add the missing tag to the translation content and import the files back to your site.
Thank you for digging into this, really appreciated.
We've sent this issue back to the translation team and they responded with 'Were the .xliff files converted from html? If so, could you send us the pages in .html format?'
I don't understand though, they were not converted and the XLIFF files should have been in the correct format already once exported, isn't that right?
No, the XLIFF file is generated from the post data, including content, custom fields, taxonomy, featured image ... everything that is translatable from a post.
the XLIFF files should have been in the correct format already once exported
Yes, as I suggested, please make a small change the page content/title > export a new XLIFF file and send it to the translation service and ask them to translate the file again.
Also, please notice that, before importing the translation XLIFF file, don't edit the page or make something else like install plugins, theme, add custom code ... that might affect the post content and data. Some page builder plugins can cause this issue.
Thank you, I've reported the issue to the translation team and they attempted to resolve it, but even with the new files they sent me, it still does not work..
I am not sure what to do or recommend to them at this point, when you checked the staging site, was everything setup on the site for it to work with elementor? Am I missing something?
