translate article

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: Bug, Custom Work

This topic contains 42 replies, has 0 voices.

Last updated by Alejandro 1 week, 3 days ago.

Assisted by: Alejandro.

Author	Posts
August 4, 2025 at 4:19 am #17291702
Bigul	Hi Alina, Thank you for the updates. I have created a new ticket for the editor warning conflict to make follow-ups easier. Please check the update in the latest ticket: https://wpml.org/forums/topic/warning-you-are-about-to-edit-your-translation-using-the-standard-wordpress-editor/ We are currently troubleshooting the issues one by one and will get back to you as soon as possible. Thank you for your patience. -- Thanks! Bigul
August 4, 2025 at 6:42 pm #17294502
alinam-2	Bigul, There are 3 issues: 1. you don't consider what I write 2. Much higher CPU/Memory needs than core wordpress, leading to php errors 3. failing html copy by WPML 1. is the worse, and your last answer proves a real lack of any consideration, and even of curiosity, what confirms that, beyond words, you don't mind. Regards Alina
August 5, 2025 at 5:28 pm #17297539
Bigul	Hi Alina, Thank you for the updates. For your kind information, I haven’t specifically mentioned the performance issues (such as significantly higher CPU/memory usage compared to core WordPress) or the problem where the translation status (gear icon) does not update after completing large post translations via the WPML Classic Editor, because we will be addressing these in the original ticket. After several attempts, I was finally able to make a copy of the site using All-in-One WP Migration and set it up locally just now. Will be troubleshooting the bugs one by one and will get back to you as soon as possible with updates. I have also created a separate ticket to track the fatal error issues. Thank you for your patience and cooperation. Please wait. -- Thanks! Bigul
August 7, 2025 at 6:28 pm #17303707
alinam-2	Bigul, Got a new bug tday I opened a post ((article) in its orginal language (FR) to revise it. And got that the attached. The post is clearly identified as in original language (FR), as URL proves its. Though, I got the warning: your translations will be lost. Sorry, it does not work normally. What could be your excuse, this time? Kind regards Alina
August 8, 2025 at 10:59 am #17305129
Bigul	Hi Alina, Thank you for the updates. It is possible that this post was originally created in English or German and then translated into French. To confirm, please open the French post in the WordPress editor (as shown in the screenshot), check the Language widget (on the right side of the screen), and make sure whether it is a translation of a post (English or German) or was originally created in French. Please refer to the attached sample images for more details. -- Thanks! Bigul
August 8, 2025 at 2:32 pm #17305747
alinam-2	Hi Bigul, It looks like it is considered in English. What is not normal. this post is a copy (made via yoast duplicate post) of the new "'problem post" that I created from scratch, in French. What means that if a post in French, and fully translated, is duplicated, then, it can be considered as in English by WPML. I tried to replicate with another post, and then it was OK. What means that it's in some cases. This leads me to think that the difference between "original" language, and English, which is the original language of WPML is not perfect. Why? Since I am not happy, currently, I tried Polygang, which has a plugin to export datas from WPML into their way of working. Except some details, for French, it's OK. For German, it's OK. For English, it's not OK. That said, on the warning panel, if I ciick on the left rectangular in white "retourner" ie go back, it makes nothing. Normal? Kind regards Alina
August 11, 2025 at 2:18 pm #17310341
Bigul	Hi Alina, Thank you for the details. I would like to continue this discussion (the French post is duplicated using the Yoast Duplicate Post plugin) in the following ticket to avoid covering multiple issues here, as this case is more closely related to that thread: https://wpml.org/forums/topic/warning-you-are-about-to-edit-your-translation-using-the-standard-wordpress-editor/ Please check if you can reproduce the issue on the staging site (where a duplicate of a fully translated French post is created in English instead of French via the Yoast Duplicate Post plugin). If you can reproduce it, kindly share the URL of the original post with the issue in the related thread. This will help us track the bug more effectively. Thank you for your kind understanding. -- Thanks! Bigul
August 12, 2025 at 6:03 am #17311890
alinam-2	Bigul, That is the point you are "merging" 2 topics which are different. This one here is originally 1. "why the translation of given post can't be saved." + 2. "why certain parts of the original post are not proposed for translations". Here, the fact that identification and copy of HTML and text by Yoast is superior to the ones of WMPL, is just about proving that WPML is anyway not optimally working. You have the post. You can thus test your "solutions" to solve those 2 issues ... which are probably linked technically, and so, could make just 1 issue. By the way, I have another super simple post where the HTML copy by WPML is failing. The other one : https://wpml.org/forums/topic/warning-you-are-about-to-edit-your-translation-using-the-standard-wordpress-editor/ is about PRODUCTS (not post) and about Woocommerce duplicate (not Yoast duplicate post). -> wp-admin/edit.php?post_type=product&action=duplicate_product Last, why do you refuse to give the former version of WPML strings translations? For use on staging. From whatever perspective (law, ethic, professionalism, ...) there is no good reason to refuse the trial on a test site Kind regards
August 13, 2025 at 6:43 pm #17318979
Bigul	Hi Alina, Thank you for the updates. I conducted detailed testing on both my local copy and your staging site after upgrading to the latest versions of the plugins and theme. The post translations were saved from the WPML Classic Translation Editor as expected for the following posts. hidden link hidden link In the earlier tests, the translations of these posts were not saving. Please verify it and let us know your feedback. We can track the following issue in this ticket: https://wpml.org/forums/topic/some-old-translations-have-been-broken/ "why certain parts of the original post are not proposed for translations" Sorry, as mentioned earlier, String Translation cannot be used to translate posts and pages directly. Doing so would require a lot of customization, which could significantly impact the site's performance. Thank you for your kind understanding. Please also review my update on the translation mode auto-switching for WooCommerce product posts: https://wpml.org/forums/topic/warning-you-are-about-to-edit-your-translation-using-the-standard-wordpress-editor/ -- Thanks! Bigul
August 15, 2025 at 4:55 pm #17324006
alinam-2	Hello Bigul, 1. The post which still can't be saved, and where HTML copy of WPML vs yoast duplicate is this one: hidden link 2. The purpose to use on staging the, say 2023 version of WPML is: 1. to demonstrate that I could do what I wrote 2. to replicate the problems. All this on all products and articles, which were not modified for a long while. If the staging site becomes slow, and even crash, I don't mind. I can even do a staging of the staging. Kind regards Alina
August 18, 2025 at 9:01 am #17326685
Bigul	Hi Alina, Thank you for the feedback. I have created a new copy of the staging site and will conduct another round of detailed testing locally. I will get back to you as soon as possible. Please wait. -- Thanks! Bigul
September 16, 2025 at 11:02 am #17405821
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Hello! The main issue is actually a small configuration on your server that needs to be increased. it's called: MaxInputVars and it needs to be increased to something bigger like 15000 (you may want to ask your hosting to do this for you). Once you do that, you'll be able to handle more fields in the translation editor and it will allow you to save all the elements there. You actually have a pretty big value (10000) but the content is so long that it requires an even bigger value (at least 10100 but it's safer to go to 15000). However please note that since this is a big content, it also depends a lot on your browser and internet connection since the loading of the page and the saving could probably be slow due to these factors. Regards,
September 16, 2025 at 11:43 am #17405952
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Let me know how it goes.