Our second-tier supporter found the source of the problem, debugging the issue with the DB dump you sent us. He escalated this issue to our developers.
We'll keep you updated here on any news regarding this issue.
>> Our second-tier supporter would like to know if, since the fix he made, you are still getting the deadlock error.
The thing is that we are not using the DEV server and database prepared for you now. If you find a bug and fix it - we would like to ask you for details, how do we fix it on the live version of the database?
Our second-tier supporter explains you have two options to fix this issue.
A. Go to WPML -> Settings -> Translation Editor -> Editor for new translations, and change it from 'Classic Translation Editor' to 'Advanced Translation Editor (recommended)'. And press the Save button.
B. To remove all entries from the icl_background_task table. To do this run this SQL line in the DB of your site.
TRUNCATE TABLE `wp_icl_background_task`;
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
The first option is not suitable for us, the second option we will try to make on DEV and check. Can you tell me, what are potential issues we may get after clearing this table? What does it affect and what should we check in this regard to make sure that nothing is broken elsewhere?
Itamar is currently off, so let me step in for a moment. I checked with the second tier about your question.
They said that the table is responsible for scheduled wpml actions, and in the context of your site there should not be any repercussions, but it should unblock the reported issue. You won't lose any translations, they are stored in different tables.
The topic ‘[Closed] WordPress database error Deadlock found’ is closed to new replies.
