Resolved
Reported for: WPML String Translation 3.2.7
Resolved in: 3.2.8
Overview of the issue
Some users have reported performance issues with String Translation when used with WordPress 6.3. These issues arise in specific scenarios and appear to be associated with strings that have the “default” text domain.
Workaround
Our team is working on a definitive solution. As a workaround, you can use the following steps:
- Backup the website
- Option 1: Go to “WPML > String Translation”, find and delete the strings belonging to “default” textdomain. (recommended)
- Option 2: Downgrade WordPress to 6.2.2
Exactly the same problem here.
Thank you for your feedback. Did you try the workaround provided?
If this didn’t help, please open a chat in our support channel.
Hi Andres, I also have this problem and I’ve already opened a support channel (https://wpml.org/forums/topic/extremely-high-cpu-usage/); just wanted to point out here that the workaround helps slightly but doesn’t fix the issue.
Our website is extremely slow as long as the WPML String Translations plugin stays active (unfortunately we can’t disable as it is part of the core structure), the number of orders we receive is much lower than usual and often we don’t even get order notification emails, as WPML is exceeding the limit of CPU usage available.
Really hope the developers will find a solution as soon as possible
Thank you for your feedback. Please follow this erratum and your ticket, we will keep you informed with any news from our development team.
Regards
Thanks, Andres.
Yes, I’ve tried it with no luck. My message was just to let you know.
I tried with the beta version (both WPML and String Translation) and it worked, but I don’t like beta versions a lot.
But to let you know, it worked, but just with beta.
It’s a problem with cache or something like that, because when I deactivated WP-Rockett, it worked.
Thanks a lot.
I’m glad to know that the beta version worked. A estable version is coming soon, we will keep you informed.
Nah, it worked temporarily, but the problem still exists.
I downgraded to 6.2.2 and it works. It’s a pity the beta version didn’t work.
Reply to my own commentary: It works with the second beta version.
Tested on Martin Cid Magazine
Thank you very much for your feedback! We update here once we have a stable version.
Same issue but only on one language.
Did you try the workaround here provided or the beta version?
Same here. Hope you guys find a workaround soon. Deleting the default domain strings partially solved the issue, at least the site is manageable.
Hey there,
Have you tried any of the workarounds here provided? Keep in mind that also the Beta version already available should address solve this issue.
Regards
Hello,
we are having the same issues with our website. Your plugin is causing non-stop errors, and is putting a huge drain on our server. Over the last two weeks, since updating the plugin, our traffic has been more than halved. It is nearly impossible for us to work on the website as the plugin causes a near constant critical error. And we are getting many complaints from visitors.
We have deleted the strings as suggested above but this did not improve anything. We tried to rollback your plugin but this is not allowed either.
When will you solve this issue? This is really taking far too long and it is unacceptable that one plugin causes that many troubles.
Hello there,
I understand your frustration and how important this issue can be. That’s why our devs are aware of this situation and we have released a beta version last week. Have you tried that version?
Regards
Hello,
Thank you for your follow up. No, I did not see the beta version. It does not appear on our plugins page. Where can we find this beta version?
Regards,
Sylvia
Hello Sylvia,
You can find in this document how to install our Beta version:
https://wpml.org/faq/how-to-install-beta-and-development-versions-of-wpml/
I hope it helps.
Regards
Hello Andres,
We have installed the beta version but see no improvement. Our server actually crashes even more often now and every singly time its caused by your plugin. It has been quite some weeks, are you close to finding a solution? It is impossible for us to work without the plugin, but the situation is really getting out of hand. We are losing customers and a lot of time trying to work on our website so the monetary loss is significant.
Regards,
Sylvia
Hello Sylvia,
I’m sorry to hear that the situation didn’t improve. However, if the beta didn’t help, it may be a different issue. I recommend you to follow your ticket and inform the supporter who is handling your case about your findings.
Regards
Hello Andres,
I don’t think it’s a different issue. Every single time we get the same message, indicating that your plugin causes the issue. We have countless error emails from WordPress also mentioning its your plugin. It crashes our server and uses up huge CPU. (we have a dedicated server so it can’t be caused by capacity issues)
Please note its the plugin WPML Multilingual CMS causing the issues. Not string translation. We can open a ticket but obviously your plugin has many issues that need fixing asap. Sorry, but going round in circles on a ticket probably would just be a waste of time. We are among many website owners encountering the same issues.
I understand your frustration but the issue reported in this erratum was solved with today’s release.
If this doesn’t help in your case, please open a ticket as we need to debug and see what is happening in your website.
Regards
I can’t download the beta version: i got ‘the download is expired ( Forbidden)’
If you encounter any issue downloading our beta, please try the procedure proposed in this document instead:
https://wpml.org/faq/how-to-install-beta-and-development-versions-of-wpml/
Hello everyone,
We release today a new WPML 4.6.6 which should solve this issue.
Don’t hesitate to make a full backup of your site before updating your WPML package.
Regards