[Assigned] Chinese translation

If you need WordPress administrator login and FTP access permissions, please let me know. You can also view previous tickets

I created a “Contact us” button in the Divi Library, as shown in Image 1.
The Chinese translation has already been done in the editor, so theoretically, when I switch the language to Chinese, I should be able to see the “Contact us” button.
However, it just doesn’t appear… as shown in Image 2.
For all other languages, the pencil icon appears, and after switching the language, the “Contact us” button can be seen.
Additionally, the English “Contact us” button has an envelope icon in the background, as shown in Image 3.
But for other language versions, the envelope icon doesn’t appear behind the button.
Both Divi and WPML are up to date.
When switching to German, the button does appear.

Hello
My article was translated through WPML, but the Chinese part was manually adjusted and translated in the WPML background instead of automatically translated
I previously followed your advice and turned on the map setting
The "Chinese" part I manually translated disappeared (as shown in the attached picture)
How can I adjust the settings so that the part I manually translated will not disappear

Because my Chinese translation was manually translated in ATE, not automatically translated using translation points in ATE
So in my case, I did not switch from WordPress translation to WPML ATE translation
In my case, I followed WPML's suggestion to change the setting in this picture
Originally it was Don't Map, and then I changed it to Map according to WPML's suggestion, and then the Chinese translation in WPML disappeared...
My Chinese translation has always been translated by myself in WPML ATE, and I have not used WPML points for translation

Hello,

I conducted a test and found that after using WPML's automatic translation, the Chinese content displayed is different from the manual translation I previously provided. Please refer to the attached screenshot.

WPML used Google Translate for the Chinese version, but since the automatic translation is inaccurate, we manually translated the content ourselves.

We do not want to use the automatically translated Chinese version.

In addition, this automatic translation has consumed some of our translation credits. Could you please assist in requesting a refund for the credits used for this translation?

It seems that WPML did not apply the existing translations from our translation memory.

After exiting the translation editor, I chose “Skip” because I did not want to save the automatic translation.

Could you please confirm whether this means the automatic translation has not overwritten my original manual translation?

Thank you!

Dear WPML Support Team,

We’ve encountered a critical issue regarding one of our translated blog posts. Specifically, the Chinese version of this article:

🔗 hidden link

On the frontend, the Chinese URL and slug exist, which indicates that the translation has been previously completed. However, when accessing the WPML translation editor in the backend, only 16% of the content appears as translated — the rest of the previously translated Chinese content is completely missing.

This poses a major inconvenience for us, as we had relied on the translated content for ongoing multilingual SEO efforts. Normally, we:

Manually translate Chinese content via WPML backend.

Automatically translate the other 6 languages via WPML’s automatic translation feature.

Only update Chinese content when changes are made to the original post.

But due to this sudden issue, the original Chinese content now appears lost, and we may need to retranslate everything from scratch — which was not the case before.

We kindly ask:

Is it possible to restore or retrieve the previously translated Chinese content in the WPML backend?

Is this a known issue or bug?

Are there any logs, revisions, or translation memory we can use to recover the content?

Please advise us on the best course of action. We appreciate your prompt support on this matter, as it directly impacts our content and SEO operations.