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
- 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 -
- 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 -

Supporter timezone: Europe/Vienna (GMT+02:00)

Tagged: ,

This topic contains 18 replies, has 0 voices.

Last updated by alinam-2 13 hours, 24 minutes ago.

Assisted by: Bigul.

Author Posts
July 24, 2025 at 8:49 am #17266503

Bigul
WPML Supporter since 01/2013

Languages: English (English )

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

Hi Alina,

Thank you for the details. I can reproduce the issue. Unable to complete the translation of the following post. Please refer to the attached images for additional information.

hidden link

Therefore, a couple of requests to track this. Upgrade the following configurations to help improve the performance of your site. Then, clear all types of caches and make sure the bug exists.

1) Increase *WP Memory Limit* to *256*(the minimum required memory limit for WPML is *128*). Please check the following links for more details

https://wpml.org/home/minimum-requirements/

https://wordpress.org/support/article/editing-wp-config-php/#increasing-memory-allocated-to-php

2) Increase the *MaxInputVars* of PHP settings to *10000*. Please check the following article for more details, or contact your system admin/hosting provider for this purpose.

hidden link

Please note that there are limitations when it comes to translating Posts (Articles) and Pages using WPML String Translation. For these content types, we need to use the WPML Advanced Translation Editor, Classic Translation Editor, or perform a manual translation via the WordPress editor. For more details, please refer to the following documentation.

https://wpml.org/documentation/getting-started-guide/string-translation/

https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/

--
Thanks!

Bigul

2025-07-24_13h57_46.png
2025-07-24_13h55_21.png
2025-07-24_13h54_56.png
2025-07-24_13h53_10.png
July 24, 2025 at 12:54 pm #17267540

alinam-2

Hello Bigul,
These settings are not the issue.
Indeed, you have access to staging, which is limited.
My original site has the settings you mention (see image), and it does not change, status is identical.
I am even more sure that it's not an issue of memory or calculations, that I duplicated this post, cut it in 4 different pieces, and it does change anything as well. For any of the 4 sections.
For your info, one of the elements that you tried to translate was formerly translated with WPML strings. And the other one is an addition, few days ago. Knowing that I had not enriched this post since probably ... last year.
For your info, I had a case open on this, say 1 year ago, the supporter spent his tme shooeting the ball in other fields (plugin, memory, etc.). Fact is that if editor was not working, string translation was. And using much less memory / CPU than the editor.
My interpretation: all what was translated via WPML strings is not translate-able nor modifiable by the editor. I just discovered that it's in another Database. So, there is a logic. For me, this way of doing is a kind of non-sense, all should be related to the original item (wheter plugin, post, product, ...) ... but not to which "tool" was used to translate.
Then, it also looks like any post, page, product .... which has been partly using WPML strings in the past, can't be changed anymore. From a customer point of view, it's a damage.
Waiting for your feedback and with my kindest regards
Alina

wpml-01.jpg
July 24, 2025 at 2:34 pm #17268089

Bigul
WPML Supporter since 01/2013

Languages: English (English )

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

Hi Alina,

Thank you for the details. I hope your live site is also hosted on Cloudways.

This may be a compatibility conflict. I will continue testing this further. Just to confirm, were these tests performed on the same staging site or the live site? If so, please share the post URLs.

I am even more sure that it's not an issue of memory or calculations, that I duplicated this post, cut it in 4 different pieces, and it does change anything as well. For any of the 4 sections.

Also, have you tried using WPML's Advanced Translation Editor? It is much easier to manage and offers several helpful features, such as Translation Memory, which can save time by automatically reusing previously translated content.

Additionally, as per the Debug Information, the max_input_vars value on your live site appears to be set to 2500. You can verify this by visiting WPML >> Support >> PHP Info.

Therefore, could you please recheck and confirm? Because when translating long posts or working with WooCommerce products, it is highly recommended to set max_input_vars to at least 10000. This ensures that all fields are processed correctly during translation.

--
Thanks!

Bigul

2025-07-24_19h49_43.png
July 25, 2025 at 6:39 pm #17271952

alinam-2

Hello Bigul,
You were most certainly right, if the settings on my Cloudways interface seemed right for my site, they were probably not implemented ... thank you for noticing it. I questioned the Cloudways team, and now, it's rectified and apprearing on WP/Tools/Information, it's image max input vars.
Following this change, I tried again to translate the post.
What is the result?
- as far as I can see, I can translate all fields / paragraphs.
- when I save, the saving can't be completed, the hour glass remains for hours ...
- when I later look at wp/articles, the given article is declared as 'under way", that's your clock wheel (see image uncompleted)
- surprisingly, when I open the translation (EN), it's declared as 100% completed (that's image though-completed)
- when I look at article in EN, well, whatever declared as translated or not, and anyway though 100% translated in WPML editor, the post remains at it was before (see faisan / pheasant, translated in WPML editor but invisible in EN post). Or see coeur saignant / bleeding heart flower, which remains in former string version.
For you to see with your eyes, I upaded the staging, to make it match with the current version of my site ... but php settings
So, all considered, I remain on my former belief: a "thing" (post, product, page) can't be modified if it were in the past partly translated via WPML strings.
Waiting for your feedback and wishing you plenty of good things
Alina

though-completed.jpg
uncompleted.jpg
max-input-variables.jpg