Skip Navigation

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.

Tagged: 

This topic contains 6 replies, has 2 voices.

Last updated by marcB-43 1 year, 10 months ago.

Assisted by: Prosenjit Barman.

Author Posts
August 3, 2023 at 8:23 am #14146805

marcB-43

On this website we experienced one strange bug (or maybe it is a default logic, but it works very strange then).

The problem is, that WPML doesn't show translated text (in translation editor) after I make changes in original text.

The algorithm looks like this:

1. I create/edit a page/post.
2. I add some text content.
3. I create a WPML translation. I finish it with 100%, save and close.
4. I make some minor changes to the text in original language of this page/post.
5. I open the translation of this changed page/post in WPML translation editor to edit it as well.
6. I expect to see my previously translated and saved texts, but instead WPML shows me in the translation field content of original page/post where I made changes (point 4).

For ex.:
1. I have this text in EN - "Lorem Ipsum is simply dummy text of the printing and typesetting industry."
2. I add a translation of this text in DE - "Lorem Ipsum ist ein einfacher Demo-Text für die Print- und Schriftindustrie."
3. I make some changes to my original text in EN - "NOT Lorem Ipsum is simply dummy text of the printing and typesetting industry."
4. Then I open WPML translation editor to edit my translation, but I see in the field content from original page - "NOT Lorem Ipsum is simply dummy text of the printing and typesetting industry.", instead of my previous translation - "Lorem Ipsum ist ein einfacher Demo-Text für die Print- und Schriftindustrie."

So the problem is that WPML for some reason rewrites in WPML translation editor my previously translated text, however on front-end it still displays my translations.
But it would be also cool, that in WPML translation editor I can also see my translations, so then I need to add only one word, that I changed in original text and not to translate my field every time from scratch when I make some minor changes in original text.

I'm using WPBakery page builder to manage my content on page, but I already tried to deactivate all plugins and use default theme, but this problem still exists.
I also tried 2 different WPML translation editors and it works the same on both of them.

What can be your suggestions of how can I avoid this strange behavior of WPML translation editor?
I can send a screen recording if it is needed.

Thank you for your answer!

August 4, 2023 at 9:41 am #14154119

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hello There,
Thanks for contacting WPML Support. I will try my best to assist you in this matter.

Thank you for briefly explaining the issue. It is very clear to understand.

In general, when you make adjustments in the default language and then proceed to update the translation, you will notice that the translation field appears blank. The default contents shouldn't be copied to other languages unless some specific adjustments are made for it.

Would you please try the steps below and check if that help to solve the issue?

- Please go to WPML > Support > Troubleshooting.
- Click on the following buttons-
-- Select the post type with which you're having the issue and click on "Synchronize posts taxonomies"
-- Clear the cache in WPML
-- Remove ghost entries from the translation tables
-- Fix element_type collation
-- Fix WPML tables collation
-- Assign translation status to duplicated content
-- Set language information
-- Fix post-type assignment for translations

Make sure to take a full backup before proceeding.

Once the process is completed, please open the default page in WordPress Editor and make a small change. Save the changes and then try to update the translation. I hope the contents will not be copied to other languages after that. Let me know how it goes.

I also can understand the importance of the feature you've mentioned. It could reduce the time to translate a lot. Our product team is aware of that maybe we will add this feature in the future.

Best regards,
Prosenjit

August 7, 2023 at 9:40 am #14162485

marcB-43

Hello Prosenjit,
Thank you very much for your answers.

I made today all of the steps that you mentioned, but this strange bug still exists.

When I changed one word in my sentence in the original language of the page and then opened the WPML translation editor it showed me for some reason again original text in the translation field (I made a screenshot).

Another strange thing is that I tested this logic on another website (with the same set-up and WPML configurations) and there everything works properly. It always shows me my content and does not just copy and rewrite it in WPML translation editor.

Can be there any other things that can cause such strange behaviour on this website?

Best Regards

Screenshot 2023-08-07 at 11.37.10.png
Screenshot 2023-08-07 at 11.37.47.png
August 8, 2023 at 6:01 am #14166825

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hi There!
Thanks for sharing more details on this issue.

After carefully reviewing the issue you've mentioned in your ticket, I kindly request you to check the errata I mentioned below which appears to share similarities with the issue you raised in your ticket.

- https://wpml.org/errata/translations-get-erased-when-editing-a-page/

Please implement the workaround mentioned in the Errata on your site and check if you're getting the expected result. After that, you will need to update the default post first and then try to update its translation. I hope it will help.

Please feel free to reach out with any thoughts or findings you may have. I will be happy to assist.

Best Regards,
Prosenjit

August 8, 2023 at 11:23 am #14168827

marcB-43

Hello Prosenjit,

Thank you very much for help!
It works like a charm now with that fix.

I just have 2 more technical questions concerning this problem:
1. As I manually changed source code of the plugin (directly in plugin's folder and not child theme), what will happen when I install next WPML update? Will this bug appear again?
2. Do you know why WP doesn't show me, that I can update my plugin to next version (from 4.6.4 to 4.6.5)? I made a screenshot for that. Or is the version 4.6.5 not available yet?

Best Regards

Screenshot 2023-08-08 at 13.11.00.png
August 9, 2023 at 11:19 am #14175165

Prosenjit Barman
WPML Supporter since 03/2023

Languages: English (English )

Timezone: Asia/Dhaka (GMT+06:00)

Hi!

Glad that the errata helped to solve the issue. Please find the answer to your queries below.

1) The solution for this problem has been added to WPML(version 4.6.5). As a result, once you update the plugin to this specific version, the bug will be solved as part of this update. You don't have to make any other changes in the code.

2) The update might not be available to all users for now but, it should become visible shortly. However, if you want, you can download the latest version(4.6.5) from your WPML.ORG account and install that on your site.

Let me know if there is any other queries or concern you may have. I will be happy to help.

Best Regards,
Prosenjit

August 9, 2023 at 2:57 pm #14176839

marcB-43

Hello Prosenjit,

Okay, perfekt.
I'll wait then for the officially release of update via WordPress.

Thank you very much for your help!

The issue is resolved now!