Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:

The classic translation editor reverts the wrong translation to the original language in two pages, although the front end works correctly.

Solution:

1- Edit the page in the default language
2- Re-translate the page
3- Add the correct translation to the Classic Translation editor
4- Save the translation

After that, the translated pages worked correctly on the editor and front end.

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 1 reply, has 2 voices.

Last updated by Osama Mersal 11 months, 2 weeks ago.

Assisted by: Osama Mersal.

Author Posts
January 9, 2024 at 11:26 am #15164067
marinoD

Hello support team,

A customer of mine told me that she was experiencing problems with translating pages and products (Woocommerce).

1) When they want to translate an existing page, she gets to see the original language (NL) on the left side and the translated version (FR) on the right side. With the translations, some sentences are still in the original language (NL). But if you go to see on the website itself, that sentence is translated. This is dangerous though, because if the client accidentally saves that page, then it will also save and display those NL texts on the website. While all the texts are already translated and thus lost.

2) On the homepage, my client had put an informative text during a migration. After the migration, she removed that text on the original NL page, but on the FR page that text is still listed. In the translations, she cannot see that text, nor is there any way to remove it. How can this be solved?

3) This customer has been translating content from her webshop for x number of years, but she says that since a short time she no longer has rights to translate products. Suddenly the message "You can only edit translations assigned to you" The customer says she never had this problem before. I went to look at translators and translation managers and she is listed there as well.

Either something is wrong with the configuration of the website, or something has become more complex in using WPML anyway. Is it really necessary to work with translators or translations or assign them to someone? Can't certain accounts just be set up to simply translate via a page or product? Could I possibly ask if you could take a look at the settings yourself to see if I haven't set anything wrong? This would be a great help.

Thanks in advance for this.
Best regards

samples.jpg
January 9, 2024 at 11:49 am #15164204

Osama Mersal
Supporter

Languages: English (English ) Arabic (العربية )

Timezone: Africa/Cairo (GMT+02:00)

Hi,

Thanks for contacting WPML forums support. I'll be glad to help you today.

1) We try to keep one issue per ticket in our forum. Continuing with one ticket per issue helps supporters focus on one issue at once and enables other users to find solutions to their questions faster.
Therefore, I've split the other issue and created a new ticket with this issue.

The second issue: https://wpml.org/forums/topic/problems-with-translating-the-home-page/

The Third Issue: https://wpml.org/forums/topic/problems-with-translating-woocommerce-products/

2) Let's check the first issue on this ticket. If the string on the default language is updated, it won't be checked as translated on the translation editor.

If this issue happens without updating the default language, please let me know.

Also, it could happen because of the site's migration.

Best regards,
Osama

January 10, 2024 at 2:14 pm #15169332

marinoD

Dear Osama,

There were only 2 pages that had this problem. Some strings were listed in the backend in NL, but displayed on the frontside in FR. If I save the backend version, that NL version comes through and the FR version disappears on the frontside. I translated and saved the texts again. The translation now all comes through correctly on the frontend. The problem was there before the migration, so won't be related to that.
For now, everything looks good and I'll keep an eye on the translation for a while. Should anything still go wrong, I'll get back in touch.

Thank you very much for the service.
Best Regards,
Marino