Background of the issue:
I am trying to translate my newly created posts using the WPML plugin. I want to translate the post by clicking next to the new post on the translate button. The issue can be seen on this page: hidden link.
Link to screen recording video: hidden link
Symptoms:
The Translations queue is looping, preventing any translations from being completed. I have already removed the plugin and cleared the cache, but the issue persists. I am receiving errors and no translation is occurring.
Questions:
How can I stop the Translations queue from looping?
Is it possible to turn off the queue functionality?
After discussing the issue with our server-side administrator and verifying that there are no issues on that side (conversation below), please note that we are currently translating using the simple editor. This only allows us to continue working for now, but the editor is not optimal for us, and it takes longer to translate. I still would like to see a solution for the error I shared yesterday.
Thanks for your support.
Kind regards Ivo
Ivo
Owner
17/06/2025 (17:11)
Thanks for helping us think of a solution. Your idea is a good one, allowing us to proceed with translation and continue working. In the meantime, WPML can search for a structural solution on their software side. Thanks
Marius Padureanu
Operator
17/06/2025 (15:18)
What if you choose the classic translation editor instead? hidden link With the classic translation editor there should be no automatic translation and you can manually translate the post. I selected it now, and cancelled the job for this post hidden link Now if you click here hidden link it goes here hidden link and you can translate the post. Is this how its supposed to work?
Regards, Simion
Flavia
Authorized User
17/06/2025 (13:59)
Hello.
The problem is not with a single post. It's the translation platform that's not working. For any article that I try to update or start a new translation, I get the same error result, instead of opening the page to edit the translation it redirects to the Translations queue page. From then on, it keeps on looping. I need a solution from WPML to fix the whole issue.
Ivo
Owner
17/06/2025 (13:53)
I will share the support with WPML. (Yes, the pending has been for over a day.) We always translate manually, but this stays in a loop and in the queue. Additionally, the issues persist.
Background of the issue:
I am trying to translate my newly created posts using the WPML plugin. I want to translate the post by clicking next to the new post on the translate button. The issue can be seen on this page: hidden link.
Link to screen recording video: hidden link
Symptoms:
The Translations queue is looping, preventing any translations from being completed. I have already removed the plugin and cleared the cache, but the issue persists. I am receiving errors, and no translation is occurring.
Questions:
How can I stop the Translations queue from looping?
Is it possible to turn off the queue functionality?
You can also translate it yourself, I think its like this hidden link and then here hidden link
The post also currently appears like this in the posts screen hidden link I found this topic https://wpml.org/forums/topic/refreshing-translation-status-5/ But they recommend making a website backup before trying it, and I'm not sure if this will solve the problem in this case. If nothing else works however, then you could try this as well.
Regards, Simion
Ivo
Owner
16/06/2025 (22:54)
I have also escalated this with WPML, but would still like you to check the error. (database) When I add a new admin or reset a user, I only see a white page and have to press the 'Back' button to return to the previous page. Something is not working well with the database. Also, in the error log, I see database errors.
Ivo
Owner
16/06/2025 (17:39)
Hi Support,
WPML keeps looping the translation. When Flavia or Ivo attempt to translate the last article, it keeps returning to the queue. Can you please help resolve this error? Thanks.
I need us to test two things. First, let's make sure the debug log is enabled so that we can see if there are any errors showing in the background. WordPress includes a debug mode that helps reveal PHP problems. Let's enable this and see if there are any errors we can locate.
To enable it, open your wp-config.php file and look for
In this case the errors will be saved to a debug.log log file inside the /wp-content/directory.
The wp-config.php is located in your WordPress root directory. It’s the same file where the database configuration settings are. You will have to access it by FTP or SFTP in order to edit it.
If you open wp-config.php and that define statement is not there, you can add it right before this line:
/* That's all, stop editing! Happy blogging. */
Please note that you’ll see everything, not only related to our Plugins. This will most likely include messages from other plugins, your theme, and sometimes even WordPress core. The messages appear all over the place.
Sometimes they appear right on top, but they can also appear in the middle of the page.
After enabling the debug mode, please try to replicate the issue. Navigate to the page where the error message being displayed. The errors will be either displayed on the screen or logged in the debug.log log file inside the /wp-content/directory.
Paste the latest lines here. No need to paste the entire log file, just 50 lines or so will do. Please censor any sensitive information.
Next, we need to test your site in minimal settings to rule out any possible conflicts. Do you have a staging site where we can test with only WPML plugins active and a default theme such as Twenty Twenty Five? If not, let me know and I can set one up on our cloudways server and send instructions for how to get a copy of your site.
I activated the debugging as requested. The debug data will go in this log here hidden link There won't be anything displayed on the website itself. But in case the log isn't helpful, could the WPML team check directly on the website perhaps?
Yes, we will be happy to check the log on the backend, we can do that if we have FTP access or using a File Management plugin. Were you able to set up a staging site so we can test minimal settings, or do you want me to set one up for you?
I have marked the next reply as private so that you can share credentials to a staging site if you have one.
Hi Support, can someone help resolve this issue with the WPML software? The support agent is not responding, and the issue of looping and errors in the translations remains. An update would be appreciated.
My apologies for the late response, we have had many supporters off yesterday and the reply time has been a bit delayed more than usual. I have been trying to create a staging site for you so we can test minimal settings, but have been unsuccessful with our cloudways servers. Can you send me a copy of your site using either the Duplicator plugin or All in One Migration plugin? That way, I can set a copy of your site up locally and run the tests I need there. I appreciate your cooperation and patience and once we can rule out a conflict with any 3rd party plugin or theme, if the issue is still happening I will immediately escalate this to our 2nd tier support. The next reply will have the private field to share the site copy.
Thank you for your update. I am unhappy with the organization of the support in WPML. I provided access to the database for multiple days, but I have received no follow-up. SmartOptions is a commercial website, which is why we paid for the plugins and get fast support. We have taken every step to give WPML the necessary information to resolve the issue. If there’s a problem with the plugin, it should be handled by WPML.
After reviewing WPML’s terms, I find them to be quite unfriendly, which discourages me from sharing my database with your second-line support.
This is the second time in recent weeks that WPML has experienced an error, resulting in a broken part of our website, which prevented us from working effectively.
The previous support agent also disappeared when the problem wasn’t resolved within a day, failing to communicate clearly about what was happening, or stopped responding.
Leaving a commercial site without a proper solution for a week is unacceptable in my view.
I will not be sharing any data with the second line support, as I find the assistance inadequate and the management style unprofessional, which I would not recommend to anyone considering WPML for their business website.
My name is Amit, and I’m the WPML Support Manager.
First and foremost, I want to sincerely apologize for the way your issue has been handled so far. I’ve read the whole support thread carefully and fully understand both the technical frustration and your concerns about the lack of timely and effective resolution, especially given the commercial importance of your website and the fact that you've already granted access without follow-up.
It appears that this is not an isolated incident, but rather a system-wide issue affecting all translations—something that warrants a deeper investigation.
To move this forward properly, I’d like to offer the following:
I'll move your case into our internal escalation system for advanced debugging. However, for that, we’ll need a Duplicator package of your site to reproduce the problem in a controlled environment.
I fully understand your concerns about data privacy. To give you full peace of mind, I am happy to sign an NDA agreement ensuring your data remains confidential and protected.
Would this approach work for you?
I assure you that once we have the site package, I will personally oversee the investigation and ensure we follow through until we understand what is happening.
