This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing an issue where Kadence blocks are duplicating in the WPML translation editor, causing unnecessary workload and confusion. Solution: We recommend updating the XML configuration for Kadence Blocks to prevent duplication. Here are the steps to follow: 1. Navigate to WPML > Settings and select 'Custom XML Configuration'. 2. Replace the existing code with the new XML code provided by our support team:
3. Open the default page in the WordPress Editor, make a minor change to the page title, and save the changes. 4. Update the translation in the translation editor and check if the duplication issue persists.
If this solution does not resolve the issue or seems irrelevant due to updates or specific circumstances, 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 the problem continues, 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.
I received some insights from the Dev team. It appears that Kadence Blocks have been registered for translation using their xPaths, which could be contributing to the issue.
To resolve this, the dev team recommended updating the configuration for Kadence Blocks. Instead of using xPath to register the blocks, we should use XML for the registration. Please follow the steps below.
- Please go to WPML > Settings and click on 'Custom XML Configuration'
- Add the following code in the text area and click Save.
- Now, open the default page in the WordPress Editor and make a small change in the page title. Save the changes.
- Proceed to update the translation. The translation editor should display the contents once for each block.
Please give it a try and let me know how it goes. I'll be happy to help if you need further assistance in this matter.
Hi Prosenjit... thanks for your mail, even though we have to admit that we have no clue what you are trying to describe (what is xml? what are xpaths?)
But we finally found the point Custom XML Configuration (after looking on this http://www.wpml.org website in our profile in vain).
In the space where you describe we should put the code, there is already some code:
****
What do you recommend?
Put the new code underneath?
Or replace the existing lines with the new code?
Will we not run into problems in the future again with all this customization?
It seems that we lost some translation (not in the "front end", i.e. on our website, but on what you call the "back end", the site of "wp-admin").
It appears that you’ve already registered some blocks. From the screenshot, I can see that the Infobox widget has been registered for translation. To proceed, simply remove the existing code for the Infobox. Then, right after the code for the Advanced Gallery block, add the code I provided and save the changes. Please refer to hidden link">this screenshot for further clarification.
Once you've completed the changes, open the default page in the WordPress editor. This is the page you were translating when you noticed duplicate content in the translation editor. Make a small change to the page title and update the translation. Check if the duplicate content issue still persists.
Please let me know if you need further assistance or clarification on any particular steps. I'll be happy to help.
However, we have sadly not been able to see any improvement.
We think there are 3 problems:
1. CODE
We are not entirely sure what code to add, even with your screenshot.
At first we got some error messages, so we thought we should not copy everything?
Is this correct? Please keep in mind that we have no idea about code.
2. DUPLICATE BLOCKS
There are still many blocks repeated, see attached screenshots.
3. TRANSLATIONS MISSING
As stated before, there are many translations (which we have carefully checked and corrected by native speakers familiar with our business) MISSING in the editor. We do not know what will happen if we approve the translation - will the text then disappear?
Hello There,
I hope you're doing well. Sorry for the delay in responding due to the weekend.
The code looks correct and should prevent the text from displaying multiple times. I tested it before sharing the solution. As for the issue with missing translation, could you check if the translation was previously added? If the translation isn’t fully completed, you won’t be able to approve it.
If the issue persists, a closer inspection will be required to understand the root cause of the issue.
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.
You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
If you previously added the translation in the WordPress Editor or Classic Translation Editor, it’s expected that the same translation won’t be visible in the Advanced Translation Editor. Translation memories are not shared across different editors, so translations entered through the WordPress Editor or Classic Translation Editor won’t appear in the Advanced Translation Editor, though they will still display correctly on the frontend. This is the reason, some translations appear blank in the translation editor.
To continue using the Advanced Translation Editor for updates, you can add the translation in the missing fields and save the translation. To save time, you can copy the translated content from the frontend and paste it into the Advanced Translation Editor. This way, you won’t need to re-enter everything from scratch.
I hope you can understand.
Regarding the duplicate translation issue in the Translation Editor, I updated the German translation of the Teamwear page and noticed that the "Advance" heading appears only once in the editor, as shown in the attached screenshot. However, the infobox block was still displayed multiple times in the editor.
To resolve this, I re-added the custom XML in "WPML > Settings > Custom XML Configuration", made a minor change to the page title, and saved the changes. While updating the German translation again, the infobox block content now appears only once, with no duplicate segments of the same block in the Translation Editor. Please check this screenshot for reference: hidden link
I hope this helps! Feel free to Let me know if you need any assistance with this or if there’s anything else I can help you with!
thank you for your answer.
We understand it, but we are deeply unhappy.
MULTIPLE PAGES:
Using your method of making a change in the English page, saving it & then checking the translated page, we can confirm that SOME of the multiple blocks disappear, but not all (see screenshots for "post halloween" and "page basket").
But this is the smaller problem.
TRANSLATION MEMORY SHARING BETWEEN EDITORS
You write: "Translation memories are not shared across different editors, so translations entered through the WordPress Editor or Classic Translation Editor won’t appear in the Advanced Translation Editor, though they will still display correctly on the frontend."
We understand this, but it seems a VERY suboptimal solution.
You also suggest: "To continue using the Advanced Translation Editor for updates, you can add the translation in the missing fields and save the translation. To save time, you can copy the translated content from the frontend and paste it into the Advanced Translation Editor. This way, you won’t need to re-enter everything from scratch."
According to our estimate approx. 1/3 to 1/2 of the translations are missing (see screenshots bandy1-4).
We handle 43 pages and 22 posts in 2 languages. So your suggestion comes down to performing this copy-paste act a full 130 times - in an editor that becomes painfully slow.
We humbly remind you that we are running our company full time and that idiot tasks like copy-pasting translations we have added earlier is more than frustrating.
There MUST be a better solution from a WPML because we believe it was a leader in its field. Please do escalate this beyond support level for a satisfying solution and let us know which steps WPML is taking to remedy this.
There is no need to experiment with AI-powered translations as long as the most basic need to have complete translations in the editor is not satisfied.
Thank you for your detailed feedback regarding the translation issues you're experiencing. I understand your frustration with the current situation, and I appreciate your patience as we work through this together.
Multiple Segments in the Translation Editor: I reviewed both the "post Halloween" and "page basket" screenshots, and I noticed that each segment in the Translation Editor contains unique text or sentences. There are no duplicates present. While the segment titles may appear multiple times, what matters most is that the content within each segment is distinct.
Regarding the Blank translation: I understand that you are deeply unhappy with the current situation, particularly regarding the missing translations in the Advanced Translation Editor and the cumbersome copy-paste process. I want to assure you that your concerns are valid, and I understand the impact these issues can have on your workflow.
Unfortunately, as mentioned, translation memories are not shared across these editors, leading to blank fields for translations made in the Classic Editor. While I understand that this is frustrating, it is a limitation of the current system, and I sincerely apologize for the inconvenience it has caused.
You can find more information about the potential issues that arise when switching between editors in the following links:
To help ease the process, I recommend the following options:
1. Continue Using the Classic Editor: If the majority of your translations were added using the Classic Translation Editor, you might consider switching back to it for your existing content. This way, you can work with the translations as they were originally inputted without needing to re-enter them in the ATE. The ATE can still be used for new translations going forward.
2. Incremental Updates: If you prefer to use the ATE for its features, you can gradually add translations for any missing segments by copying the translated content from the frontend as needed. I understand this is not ideal, especially with the volume of content you are managing, but it would help maintain consistency in your translations.
I understand that you would like this issue to be escalated beyond support. However, as it stands, there is no current feature to retrieve data from one editor to another due to the structure of our system. I will ensure that your feedback is documented and considered in future updates to the WPML system. Your insights are invaluable as we strive to improve our services.
I genuinely appreciate your understanding and am here to assist you. If you have any further questions or need additional assistance, please feel free to reach out.
We now tried switching from classic to advanced editor & back, both for old and new translations. No improvement.
As you can see from the screenshots, the result is disappointing in all cases - we have the choice of either lacking lots of translations (classic editor) or having some "translations" displayed in English (advanced editor).
From our web research, it is quite obvious that lots of people have this issue since the introduction of advanced editor in July 2024 , and we do hope that WPML takes this serious enough to find a solution.
We appreciate that you write that "CURRENTLY" there is no such feature, and we hope that WPML is working on a remedy. Otherwise, savvier companies like Open AI and similar will take your place, and given that we've lost hours of work on this, we'd be keen to switch to a more customer-friendly service that does not feel like it is eating/hiding our translations.
Thank you for your feedback and for sharing your experience with both the Classic and Advanced Translation Editors.
I’d like to clarify that the issues with switching between editors are not specific to recent updates to the Advanced Translation Editor. From the start, WPML has recommended selecting one editor/translation method — either the Classic or Advanced Translation Editor — based on your needs and using it consistently throughout your workflow. Switching between editors can lead to translation gaps, as the translation memories in each editor are not designed to be shared or integrated.
While a feature to share translation memory or to retrieve content between editors is not currently available, we recognize the value it would provide to our users. Please rest assured that we are actively exploring options to make this possible in future updates, as part of our commitment to improving WPML based on user feedback like yours.
Given the limitations associated with switching editors, I recommend following the advice shared in my previous responses. I would be more than happy to guide you for your specific workflow.
Thank you again for your valuable feedback. We appreciate your business and your trust in WPML. If there’s anything more we can do to help, please feel free to reach out directly.
Thank you, Prosenjit - so it is what it is.
For future users, it would be great to make the information about different editors MUCH more prominent and clear.
