issues product translation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client needed assistance with database tables related to WPML, specifically those missing the AUTO_INCREMENT attribute, which could potentially affect both WPML and non-WPML tables.
Solution:
We recommended the following steps to address the issue:
1. Install the Adminer plugin on the live site to manage the database. Alternatively, use any preferred database management tool.
2. Open the database and compare the WPML tables (with the _icl_ prefix) against those on the staging site.
3. Identify any tables where the primary key column lacks the AUTO_INCREMENT attribute and refer to the previously shared screenshots for guidance.
4. Open the table, click 'Alter table', enable AUTO_INCREMENT for the appropriate column, and save the changes.
Additionally, we advised the client to review other non-WPML tables, as the issue might extend beyond just WPML-related tables, suggesting a broader problem with the database structure.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum at https://wpml.org/forums/.

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: Exception, WCML

This topic contains 19 replies, has 0 voices.

Last updated by Andrey 3 weeks, 1 day ago.

Assisted by: Andrey.

Author	Posts
June 4, 2026 at 4:19 pm #18082253
sohailaH	Hi,, i want to continue previous ticket "" https://wpml.org/forums/topic/issues-product-translation/ "" i prepare to you staging site and ftp account as you ask me, can i send to you in private ? thanks ,,
June 5, 2026 at 3:44 pm #18084305
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for contacting WPML support. The previous support ticket has already been closed. Could you please describe the issue you are currently experiencing and provide as many details as possible? I will be happy to investigate it further. I have set my next reply as private so that you can safely provide access credentials to your staging site if needed. Please include any relevant information, such as: * Steps to reproduce the issue * Links to affected pages * Screenshots or screencasts, if available * WP-Admin and FTP access credentials This will help me troubleshoot the issue more efficiently.
June 6, 2026 at 5:37 pm #18085266
sohailaH	i sent to you description of problem and credentials you ask in private
June 8, 2026 at 1:52 pm #18087680
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for providing the details. Unfortunately, I am unable to log in to your site. Whenever I try to access the WordPress admin area, I receive a 404 Not Found error. Could you please verify that the login URL is correct? To ensure that each issue receives the attention it deserves, could I kindly ask you to open a separate support ticket for each issue you mentioned? Please include detailed descriptions and screenshots for each one. This helps us track and investigate each problem more effectively. For this support ticket, I will focus specifically on the following issue: HTTP 504 Gateway Timeout Once I am able to access the site, I will continue investigating this issue further.
June 8, 2026 at 2:21 pm #18087884
sohailaH	please open aprivate area to send credentials again
June 9, 2026 at 7:07 am #18089009
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Sure. I have set the following reply to private.
June 11, 2026 at 8:48 pm #18097817
sohailaH	i send all details privately
June 15, 2026 at 1:15 pm #18103939
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for providing the details. Unfortunately, I am unable to log in using the credentials provided. I am receiving the following error message: Error: The password you entered for the username te*********er is incorrect. Could you please verify the credentials and update them if necessary? I have set my next reply as private so that you can safely share the corrected access details. Once I am able to log in, I will continue checking the issue.
June 16, 2026 at 1:08 pm #18106916
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for providing the updated access credentials. I have looked at the first issue, the following: 1. Translation Dashboard & Sync Failures Loading & Performance: The translation interface takes forever to load and frequently hangs (infinite loading screen) without opening. Once, I temporarily renamed the mu-plugins folder in your staging site, which contains the custom files, and ran troubleshooting options in WPML → Support → Troubleshooting. I can no longer replicate this issue with loading the Translation Dashboard. I have Can you confirm this, please? I have also updated WPML plugins on your staging site. I recommend updating the remaining plugins and the theme if required. Let me know how it goes, so I will create a new support ticket for the issues you have mentioned.
June 16, 2026 at 5:57 pm #18107458
sohailaH	Hi Andrey, Thank you for your support. I have some critical updates and a new issue that needs to be addressed on the staging site before we push the final fixes to production. Here is what I have done so far on my end: I have successfully updated all active plugins on the site. I temporary renamed the mu-plugins folder as suggested. The New Issue (Infinite Translation Queue Loop): I added a new test product named "ayat", and sent it to translation. However, it got duplicated infinitely in the translation queue (as shown in the attached screenshot image_df4d5b.png). When I click on the "Translate" button, the system keeps looping, fails to open the translation editor, and continuously redirects me back to the same page with the infinitely duplicated product list. Also, the queue section keeps stuck on loading (as shown in image_df48b9.png). What I need you to do: Please investigate and fix this infinite loop and duplication issue directly on the Staging Site first. Once this duplication bug is fully resolved and tested on staging, please proceed to apply the exact same fixes, database troubleshooting, and WPML updates to my Live/Production Site . "Please note that you don't have the credentials for my Live Site yet. Once everything is fully resolved and tested on staging, please let me know and request the Live Site credentials so we can safely apply the final fixes together." "Also, one more quick question regarding core updates: I noticed that WordPress version 7.0 update is currently available in my dashboard. Could you please let me know if WPML is fully compatible with WordPress 7.0, or should I hold off on this core update until we fix the current database issues?" Looking forward to your findings. Best regards,
June 17, 2026 at 6:52 pm #18110178
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for your feedback. I was able to reproduce the same issue on the staging site and investigated it further. During my analysis, I found that the root cause appears to be database corruption. More specifically, several database tables are missing their required AUTO_INCREMENT properties, including some WPML tables. This issue is not limited to WPML. While reviewing the site’s debug log, I found multiple database errors related to WooCommerce tables, such as duplicate primary key errors in the wc_admin_notes table. These errors indicate that records are being inserted with the same primary key value because the AUTO_INCREMENT setting is missing or incorrectly configured. [16-Jun-2026 20:36:21 UTC] WordPress database error Duplicate entry '0' for key 'PRIMARY' for query INSERT INTO `_wc_admin_notes` (`name`, `type`, `locale`, `title`, `content`, `status`, `source`, `is_snoozable`, `layout`, `image`, `is_deleted`, `is_read`, `content_data`, `date_created`, `date_reminder`) VALUES ('wc-admin-edit-products-on-the-move', 'info', 'en_US', 'Edit products on the move', 'Edit and create new products from your mobile devices with the Woo app', 'unactioned', 'woocommerce-admin', '0', 'plain', '', '0', '0', '{}', '2026-06-16 20:36:21', NULL) made by do_action_ref_array('wc_admin_daily'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\Admin\Events->do_wc_admin_daily, Automattic\WooCommerce\Internal\Admin\Events->possibly_add_notes, Automattic\WooCommerce\Internal\Admin\Notes\EditProductsOnTheMove::possibly_add_note, WC_Data->save, WC_Data_Store->create, Automattic\WooCommerce\Admin\Notes\DataStore->create [16-Jun-2026 20:36:21 UTC] WordPress database error Duplicate entry '0' for key 'PRIMARY' for query INSERT INTO `_wc_admin_notes` (`name`, `type`, `locale`, `title`, `content`, `status`, `source`, `is_snoozable`, `layout`, `image`, `is_deleted`, `is_read`, `content_data`, `date_created`, `date_reminder`) VALUES ('googleforwoocommerce_q2_2026', 'marketing', 'en_US', 'Limited-time offer: Get 2x your ad spend back in Google Ads', 'New to Google Ads and based in the US? Launch your first Google Ads campaign before June 30 to receive double your ad spend back as Google Ads credit. \r\n\r\nUse new GenAI tools, YouTube Shopping, and Performance Max campaigns to sell more with WooCommerce and Google — get started today.', 'pending', 'woocommerce.com', '0', 'plain', '', '0', '0', '{}', '2026-06-16 20:36:21', NULL) made by do_action_ref_array('wc_admin_daily'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\Admin\Events->do_wc_admin_daily, Automattic\WooCommerce\Admin\RemoteInboxNotifications\RemoteInboxNotificationsEngine::run, Automattic\WooCommerce\Admin\RemoteInboxNotifications\SpecRunner::run_spec, WC_Data->save, WC_Data_Store->create, Automattic\WooCommerce\Admin\Notes\DataStore->create Based on what I found, I suspect this may have been caused by a database migration, a restoration process, or a third-party plugin or tool that modified the database structure. To verify this, I manually corrected the AUTO_INCREMENT settings for the affected WPML tables on your staging site. After doing so, the issue could no longer be reproduced, which confirms that the missing AUTO_INCREMENT configuration was causing the WPML-related problems. To resolve the issue on the live site, I recommend comparing the database structure between the staging and live environments, paying particular attention to the tables that begin with the _icl_ prefix (WPML tables start with _icl_). Any table that requires an AUTO_INCREMENT field should have it restored to match the staging site’s structure. I also strongly recommend reviewing the rest of your database, as the issue appears to affect more than just WPML tables. The WooCommerce errors suggest that other tables may be missing AUTO_INCREMENT settings as well, which could lead to additional problems throughout the site. I have attached screenshots with comments highlighting the the issue and the changes that were made on the staging site for your reference.
June 19, 2026 at 1:14 pm #18115018
sohailaH	Hi Andrey, Wow, thank you so much for this incredible and deep technical investigation! You have truly found the root cause that has been causing us so many headaches across the site. Finding the missing AUTO_INCREMENT database corruption is an absolute lifesaver. I am so glad to hear that the translation loop issue is completely resolved on the staging site thanks to your manual database corrections. Since you already know exactly which tables are corrupted and how to fix them, could you please request the credentials/access for our Live (Production) Site? I would be extremely grateful if you could apply the exact same database fixes to our live environment to ensure everything becomes fully stable there as well. Please let me know what credentials or access tokens you need, and I will provide them immediately. Thank you again for your outstanding support!
June 22, 2026 at 12:59 pm #18118409
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	I appreciate your feedback. Since you already know exactly which tables are corrupted and how to fix them, could you please request the credentials/access for our Live (Production) Site? I would be extremely grateful if you could apply the exact same database fixes to our live environment to ensure everything becomes fully stable there as well. Yes, sure. The following reply is private, so please provide the access credentials (including FTP access). I will also need to install the Adminer plugin on your site to access the database. Please ensure that you back up your database first.
June 24, 2026 at 10:19 pm #18124618
sohailaH	I understand the issue. Since this requires live database structure changes, I will take a full backup first. Can you please send me the exact list of affected tables and the exact ALTER TABLE queries you applied on staging, especially for the WPML _icl_ tables and WooCommerce tables like _wc_admin_notes? I prefer applying the same confirmed SQL changes on live instead of manually guessing the AUTO_INCREMENT columns.
June 25, 2026 at 1:30 pm #18126240
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	Thank you for your feedback. Unfortunately, I did not make a note of the specific tables that were affected. The best approach is to compare the database structure between your staging and live environments, focusing on the tables with the _icl_ prefix, as these are the WPML tables. Any table that should have an AUTO_INCREMENT field should be updated to match the structure of the corresponding table on the staging site. You can do this as follows: 1. Install the Adminer plugin on your live site (or use another database management tool if you prefer). 2. Open the database and compare the tables with the _icl_ prefix against those on the staging site. 3. Identify any table where the primary key column is missing the AUTO_INCREMENT attribute (please refer to the screenshots I shared previously). 4. Open the table, click Alter table, enable AUTO_INCREMENT for the appropriate column, and save the changes. I have attached screenshots again for your reference. Regarding the other database tables, I did not modify or repair them. I only checked and corrected the WPML (_icl_) tables. However, during my investigation I also noticed that some non-WPML tables, such as _wc_admin_notes, were missing the AUTO_INCREMENT attribute as well. This suggests that the issue is not limited to WPML tables and may indicate a broader problem with the database structure. For that reason, I strongly recommend reviewing the rest of your database tables to ensure their structure is correct. I hope this helps.