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.

This topic contains 1 reply, has 2 voices.

Last updated by Dražen 1 year, 5 months ago.

Author Posts
December 18, 2023 at 7:08 pm #15087027

thomasA-35

I am trying to:
Independently translate an English translation of a German page.

Link to a page where the issue can be seen:
hidden link
hidden link

I expected to see:
After translating the German page via the Translation Editor, the English translation should be saved.

Instead, I got:
The translation seems to be stuck in a "Duplicate" mode. Every time when the original German page is saved, the English translation disappears and is overwritten with the German original.
When I try to translate it again, the Translation Editor tells me its a duplicate. I then choose to edit it independently and save the translations.
This is where the loop begins again - as soon as the original is edited, the English translation is overwritten again.

Bildschirmfoto 2023-12-18 um 20.02.30.png
Bildschirmfoto 2023-12-18 um 20.00.25.png
December 19, 2023 at 8:53 am #15089819

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

Probably something is blocking WPML from setting this post as an independent post, please try the next method.

Please make a backup before proceeding.

FIX
To fix this, we just need to edit the database and remove the entry for your POST (POST ID) in the wp_postmeta table with the key “_icl_lang_duplicate_of”.

Go to your post meta table and find key _icl_lang_duplicate_of with your post ID, and delete it.

Then please check if the issue still happens, it should work fine now.

You can also delete all _icl_lang_duplicate_of keys if you wish.

Please let us know how it goes.

Regards,
Drazen

December 19, 2023 at 10:13 am #15091107

thomasA-35

Thank you Dražen for your support, deleting this entry from our postmeta table fixed the issue for us.

Regards,
Thomas