This thread is resolved. Here is a description of the problem and solution.
Problem: The client was unable to translate all content on a custom products post type created using Elementor and an ACF gallery field. Only specific sections were available for translation in the WPML Translation Editor, despite trying various troubleshooting steps such as resaving permalinks, updating software, and disabling advanced translation editors.
Solution: 1) Ensure that all Elementor Widgets used are supported by WPML. WPML supports widgets from Elementor and Elementor Pro by default. If using widgets from other sources like 'Ultimate Addons for Elementor Pro', ensure they have an XML configuration for translation. More details can be found here: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/ 2) Check the translation preference settings for the ACF Field Group. If set to 'Expert', adjust the settings accordingly. 3) Update all WPML plugins to their latest versions. 4) Disable any potentially conflicting plugins temporarily to check if they interfere with the translation process. 5) If issues persist, consider sending the page for translation again through WPML > Translation Management, and then take and translate the job.
If this solution does not resolve your issue or seems outdated, we highly 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
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 translate a custom products post type created using Elementor and an ACF gallery field. I created a test post to translate some texts used across all products. I followed this article: https://wpml.org/forums/topic/elementor-text-widget-not-recognized-or-translated/. The issue can be seen here: hidden link.
Symptoms:
Only section 1 and section 2 (Weight, Expiration date, etc icons and texts) show up for translation, and nothing from the rest of the content. I tried resaving permalinks, updating all software, resaving the post and its translations, disabling the advanced translations editor, and even deleting one test post and creating a completely new one, but nothing changed.
Questions:
How can I fix the issue of not being able to translate all content on the page?
Why are only certain sections showing up for translation?
I just wanted to update the link for the page where the issue can be replicated because we made some changes to the permalink structure to address other translation issues.
If the author does not provide such a config, you can alternatively create one yourself. This config can be stored under WPML > Settings > Custom XML Configuration.
We can further offer a WPML test site on which we can recreate the issue and I assist you with a basic configuration for a couple of widgets, but if there are many affected widgets it would be better to reach the author of those widgets.
---
Also, please let us know which translate preference setting your ACF Field Group is using. If you use the "Expert" settings please let us know which settings your fields are using.
The fields in which we encounter issues aren't ACF or dynamic fields, they are standard Text Editor fields.
The only "special" field is an Elementor Pro Loop Carousel field with a template but we use the exact same field on other posts and they are translated without any issues.
The translation is done using WPML Translation Editor and although we refer to the post in question as a template it's not a dynamic single template or anything like that, it's just a post with design and structure that will later be duplicated using a plugin as a template.
If needed, I can provide temporary access to the staging environment so that you can take a look.
Let me know if my answer provides all the information you need about the issue.
- 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, indeed the EN translation editor shows all the fields now.
I also see that there are some changes to the way fields are displayed in the editor now.
Can you please walk me through the steps to fix it?
The translation editor in Greek still shows only the first few fields.
I don't notice any plugins being left deactivated, nor have any icons been removed from the original language version.
I want to make sure we would be able to handle this in all languages and future cases too.
We tried the steps you suggested when translating another product but we encountered errors similar to the errata you mentioned.
After changing the DB collation, it seems to have been fixed.
However, we noticed that when starting a new translation for products, we're taken first to the Translation Queue. Without any action, if we edit the same product translation, we're then taken to the translation editor.
We tried the solution mentioned here https://wpml.org/forums/topic/translation-queue/ but that didn't give any results.
Is there a way to skip going to the queue first and go straight to the editor?
Thank you.
New threads created by Dražen and linked to this one are listed below:
Thanks for getting back, glad to hear it works fine now.
We limit 1 issue per ticket to keep things clear. This will help other users with similar problems to find solutions when searching the forum.
I have opened a new ticket for your other issue, as this should not happen, you should be able to start translation in the translation editor:
- https://wpml.org/forums/topic/split-when-starting-translation-were-taken-first-to-the-translation-queue/
If it is okay lets close this ticket now since seems no more doubts about the topic.
