Hi Bigul,
In addition to former message ...
There is bot a database and html issue.
I made some additional tests.
Some old translations have been "broken" by WPML changes. I found out 3 different cases:
- when paragraph was containing a link
- when paragraph had bold (ie
- and apparently also when paragraph contained quotation marks
Also, the translations that were in the past recorded and thus re-usable, are not anymore.
Could you explain?
Kind regads
Welcome to the WPML support forum. I will do my best to assist you in resolving the issue.
I have created a separate ticket for this one to make follow-ups easier and to avoid discussing multiple topics in a single ticket. This will help us support you more effectively.
I did a quick check in our records and couldn’t find any similar cases with the recent versions of WPML when using the Classic Translation Editor.
Therefore, I have a couple of requests:
- Please share the URLs of the posts where you are seeing this issue.
- If possible, include a few screenshots to help us understand the problem better.
We will continue debugging this alongside the main ticket. Thank you for your cooperation.
Hi Bigul,
You place me in a deadend.
This issue happens on post where I used WPML strings & editor
You refuse me to use strings again.
By definition, and because of your decision:
- I can't identify where issue could be (ie on which post I used strings)
- I can't reproduce it.
You made changes in WPML, without warning.
Without letting people prepare the change.
And now I am a with considerable non-usable quantity of work
I consider it as a shame.
Kind regards
Thank you for the updates. For your kind information, the Classic Translation Editor was introduced many years ago. Therefore, we would like to know how long you have been using WPML on this site.
Additionally, it would be helpful if you could share the URLs of the posts where you are experiencing this issue, apart from the following one, if any.
hidden link
We will do our best to identify and resolve the issue you are facing as soon as possible. Thank you for your kind understanding.
Bigul,
Again, this is a kind of bad faith
When you refuse me to use old version of WPML strings, you don't enable me to identify where the problem is as well.
Dead end.
The only thing I can add, is that you did not consider what I wrote in another .... thread: the HTML copy made by WPML is incorrect
Kind regards
Thank you for the updates. I am currently consulting with our developers regarding this.
One request: could you please share a screencast demonstrating the issue mentioned below for better understanding? It would be very helpful for our internal discussions and further troubleshooting.
I wrote in another .... thread: the HTML copy made by WPML is incorrect
If possible, please show how the issue occurs when translating or duplicating a post into secondary languages.
Since we have discussed multiple conflicts you are facing, we just want to make sure we are not missing any important points. Thank you for your kind understanding.
1) What I did re. the post with problem, since I need it, it's very important for me.
I created a new article, wheere I copied / pasted the full code of the original article (in FR)ock
Then, I opened translations.
- Most translations, say 80% were already there.
- The paragraphs where were bold html tags or quotations marks had to be translated again.
- plugin codes (modal block), was pre-filled
Since 80% of paragraphs were alreayd there, except those with quotation marks and html tags, there is a reason.
Then, I tried to replicate this. Opened new article, copied / pasted the full original FR code ... and opened a translation, and then, all was to be translated again.
My interpretation: WPML did that so that all translations are re-done. Since, in most cases, it will be done automatically, this will lead to additional fees for WPML.
2) As you know, when editing translations of the "problem post", recent fields are missing. If I duplicate the same post, using Yoast duplicate post, then all fields are there.
An additional proof that the html identification and copy does not work for WPML.
Forget about a memory / max inputs, it is not the problem, that's 100% sure, I spent many hours to fully re-do the post, and translations work.
Here, the conclusion is that if a change occurs on old post or old product (see other thread), because of new WPML, it does not work. And everything is, probably deliberately, totally lost so that people pay new automatic translations.
Thank you for the details. I did a few rounds of testing on my local copy, but was not able to reproduce the issue exactly. Therefore, just to confirm, have you ever switched to the WPML Advanced Translation Editor on the live site?
Also, could you please share the URL of the post from which you copied the content to create the new one? Was the original post created using the Block Editor (Gutenberg) or WPBakery Page Builder? This information will help us better track the issue. Does the problem also occur with Product posts?
While testing further, I noticed a related bug that is reproducible on your staging site, also. When a post is duplicated using Yoast Duplicate Post, it is correctly duplicated in both the original and secondary languages as Drafts. However, after making changes to the French post (original) and publishing it, the translation mode switches from the WPML Translation Editor to the WordPress Editor.
We will continue investigating this behavior and will update you shortly. Please refer to the following screencast for more details.
Bigul,
The "funny" thing:
- I can show and prove that I managed to translate the problem post, update it, re-translate, without any issue. By doing as I wrote. I can even add new element, to prove it.
- Knowing that, I tried to replicate the same, for you, on staging. But when I did ... if the "old" translations" were present on live site, they were not on staging. Why? I don't know. my interpretation is that WPML added something in program that deletes old translations, whether they are from editor or from strings.
To change post, I did what I said, then changed URL of old post, then used old URL for new post. Dates should confirm that, I can either update staging, give your access to my live site, and you can see on current URL that the glyphs (see former elements in thread about what was mssing in HTML copy) are now translated ... and enriched with addition info: hidden link
As to your second point ... I can't tell you why, of course, but there is obviously a different behavior between staging and live sites. My interest is to prove that the issue can be replicated. When I created a new article by coyping the "problem post code", I got different pictures.
If I link with discussion on product, where WPML decided that some products were not translate-able via editor, even if they were couple of years old, there is "something" / conditions that decides if it's in new WPML queue or not ... and if for whatever reason it's "out", translation is lost.
Thank you for the details. I am consulting with our second-tier team about this.
We understand that the issue occurs on your live site, but we could not reproduce it exactly on the staging site or our local copy. We have also noted your points about missing old translations, the differences in behavior between live and staging, and your method of updating the post by changing URLs.
Since we already have access to the staging site and a local copy, could you please share the exact step-by-step actions you took on the live site when the issue occurred? It would be very helpful if you could also provide a screencast for better clarity, as this will assist us greatly in our internal communication and while escalating the ticket to our development team.
Thank you for your patience and for the time you have spent testing this.
The same tactic of placing me in a dead-end by refusing to give the info and tools I need.
Q1: Why do you refuse to give me the old version of strings?.
Q2: why WPML changed translations of copied post?
Say, I create a post X, and translate it in 2 languages.
I copy / paste in the X post content in a new post, called Y
In past, most translations of X content were present in Y, now, they are not.
WHY?
Hello Bigul,
I hope that you are doing well.
Sorry for late feedback, I have been on holiday for a week, I needed to rest fir a while.
Re. products, the attached image, already sent in another ticket, clearly shows that there is a problem.
Re. post / article, what did I? For the post that can't be saved, I copied the FR code (gutenberg editor) in a brand new article. When I first opened the EN translation (in WPML editor), old "translations" (ca 80%) appeared. Meaning they were kept in memory.
Those absent were those with , quotation marks, and links.
If I repeat the same, it does not work, because nothing is kept in memory.
=> Why this can't be reproduced, you know it. My interpretation is that WPML recently disabled this "keep in mind old translation"
So, if you want to reproduce it, please, give the old version of WPML, without this translation queue. Or explain why WPML does not enable to get "old translations".
Further, I noticed another weird thing. I only work with wp editor (ie not wpbakery, elementor, divi, or any other). For posts, WPML translations sees paragraphs as "Paragraph". And for products, it's identified as "core/paragraph".
So, ccould you please be fair and explain why translations were kept in mind, and are nomore now?
Bigul is currently on vacation, so I’ll be handling this ticket for now—hope that’s okay.
Could you please provide some additional details regarding the following:
Were the missing sections previously translated using WPML → String Translations?
You can still locate post and page-related strings in WPML’s String Translations. To do so, go to WPML → String Translations, then open Screen Options at the top and enable Page Builder Packages.
While this option was visible before, using String Translations for these cases was never the recommended method, as it could cause missing translation issues. For this reason, it has been hidden in newer versions to help avoid confusion.
Were there any modifications made to the affected sections?
Additionally, do you happen to have any posts or pages where I can reproduce the issue (where only 80% is displayed in the CTE)? This would help me investigate further and understand why it occurred.
Looking forward to your response.
Thanks
The topic ‘[Closed] Some old translations have been broken’ is closed to new replies.
