Skip to content Skip to sidebar

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.

Sun Mon Tue Wed Thu Fri Sat
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

This topic contains 23 replies, has 1 voice.

Last updated by Andreas W. 1 month, 1 week ago.

Assisted by: Andreas W..

Author Posts
May 21, 2026 at 5:19 am #18049926

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello nicoW-9,

I understand your frustration, and I appreciate your patience.

When using WPML, you have three translation methods:

1) WPML Translation Dashboard
2) WPML Translation Editor
3) WordPress Editor

The translation method can be defined for each piece of content in the right sidebar of the WordPress Editor. Currently, your example is using the WordPress Editor as the translation method.

If you want to translate the content using the WPML Translation Editor, please ensure to set the proper translation method in the sidebar while editing the original content.

It's important to avoid editing translated content directly in the WordPress Editor if you are using the WPML Translation Editor or WPML Translation Dashboard, as those changes will not be recognized by the WPML translation UI and may be overwritten during the next translation job.

Key finding: Always stick to the translation method defined for the original content to ensure consistency.

If you encounter issues with translations created through the WPML Translation Dashboard or the WPML Translation Editor, please let me know, and I would be happy to investigate further.

In this case, please provide an example of content and the detailed steps you are taking, so that we know how to replicate the issue.

Thank you for your understanding.

Best regards,
Andreas

May 21, 2026 at 12:02 pm #18051443

nicoW-9

Hi, so finally the direct answer to what i needed to know to fix the setting.

Now the new issue arrises and i noticed, as the warning said, that WPML did not remember any of the previously made translations which means 2 attempts top fully translate all posts are lost and i will need to hire someone again to fully translate all posts.
I don't know if its 1 more inherent flaw in wordpress or if it's a flaw in wpml. At least it's a flaw that wpml lets me translate (read: waste time and effort) posts that are set to iggnore the translations.

I am willing to make a deal: if wpml supplies me with the credits that account for fully translating my posts so after months of use it's finally showing the wanted results, i am willing to give a 4 star rating for at least helping out to get my translations done.

If i will need to hire a translator again, that would result in a different opinion about the solutions.

May 21, 2026 at 8:43 pm #18052841

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Thank you. Please allow me this follow-up question, as I need to understand exactly which workflow you applied.

Does this mean that you created translations using the WordPress Editor, while actually having the WPML Translation Editor set as the translation method?

If so, the issue is expected, and WPML`s UI gives warnings if you try to edit translations on the WordPress Editor while the content is supposed to be translated with automatic translation or the WPML Translation Editor.

May 22, 2026 at 7:27 am #18053248

nicoW-9

Now i'm certain, if this is not due to your intellect, that you are doing it 100% on purpose! I have said multiple times how the situation was so i'm not even going to bother doing it again and you are purposefully asking if i did it in another wrong way + adding imaginary warnings just to try and imply it was my mistake.

If you wish it to be my mistake, it's ok. I'm at a point now whaere wpml can do no good for me here, sad to say.

I will document this ticket and ask a manager if this is an isolated case or if this is wpml policy and act accordingly.

May 22, 2026 at 8:07 am #18053354

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

You reported on this ticket:
"images in translated posts didn't show because there was a certificate issue"

This was investigated, and the cause was explained in a prior comment:
https://wpml.org/forums/topic/issues-with-translated-posts/#post-18048252

You also reported:
"that means yes i use wpml to update posts edits but they don't overwrite the translated posts"

This was also investigated, and there was no issue with updating a translated post inside the WordPress Editor.

If your site still experiences issues, please provide an example and exact steps.

May 29, 2026 at 11:24 am #18069344

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

My apologies for the delay in answering.

May I ask how you moved the site from development to production? I would like to understand how this issue occurs. If you use a proper migration plugin, you should never run into such issues. This usually only occurs if you use the same old database after having changed the site's domain.

I have been working on your site and assisted you with fixing the image source issues on your affected posts.

Here is what I did so far:

1) I synced the media to make sure the media files are available inside the media library in each language

2) Manual Image fixes on post translations

DONE Rood Licht Therapie voor Dummies NL > DE
DONE Mannendingen NL > DE

DONE Intiemzone lichttherapie NL > EN
DONE Huid gezondheid en collageen NL > EN

Both languages affected
DONE 7 tips om je Collageen te Boosten – tip 2 is revolutionair
DONE Therapie lichten uit China van wish of aliExpress
DONE Gezonder leven met de adviezen van Iris de Goede
DONE Blauw licht filter brillen: wat zijn de gezondheidsvoordelen van blue block brillen?
DONE Roodlichttherapie: de toekomst van gezondheid met NorahLux
DONE Rood Licht Therapie en Vitamine D
DONE Erectiestoornissen en vruchtbaarheid
DONE Blauw licht ‘junk light’
DONE Kun je afvallen met rood licht therapie?
DONE Spiermassa en energie

There are a few open issues. For example, translations are saved inside the WPML Translation Editor but not rendered on the Frontend and Backend of the translations.

Post Translation fix

OPEN Intiemzone lichttherapie NL > DE
OPEN Huid gezondheid en collageen NL > DE

Another issue is that, even though there are product variation images on the backend when inspecting translated products, those images do not show up on the frontend.

Further, I can confirm that various products have been translated inside the translation editor, but the translations are not showing up on the site.

I took a local copy of your site to investigate those issues and I need to ask you for some more patience. If you have any questions or other issues to report, please let me know.

May 31, 2026 at 5:48 am #18071260

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

I have been investigating the issue about translations not showing up on translated posts that were translated using the Advanced Translation Editor.

On a local copy, I translated the posts Intiemzone lichttherapie when testing the site without using different domains per language.

Then I tested the post Huid gezondheid en collageen from NL > DE while using a different domain per language, and I was able to replicate the issue.

I need some more time to investigate the cause of this issue, and I need to ask you for some more patience.

Also, there are currently many updates available on your site. Please run the available updates after having taken a backup of your site, including the database.

June 2, 2026 at 2:26 pm #18076133

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

I have kept testing, and so far I can confirm that this issue is not theme-related.

If I test only with WPML and WooCommerce, the translation works out using the Advanced Translation Editor.

This means one or more third-party plugins are causing the unexpected issues. I need to ask you for some more patience, as testing is very time-consuming in this case.

I need to bascially test the translation many times, while disabling plugins one by one.

Sidenote (not related to the ATE issue):

Note this notification on the dashboard:

⚠ The Legacy REST API plugin and HPOS are both active on this site.

Please be aware that the WooCommerce Legacy REST API is not compatible with HPOS.

You should disable the WooCommerce Legacy REST API plugin.

June 3, 2026 at 11:47 am #18078484

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

I do not see any issue with creating a new post on a copy of your site and translating it with the Advanced Translation Editor.

The posts from your example were created in 2018.

I needed to edit the original content, go through the block, and use the option "Convert to Blocks".

After that, the translation works out. Please give this a test.

The topic ‘[Closed] Issues with translated posts’ is closed to new replies.