Problems with finishing setup

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

Problem:
While setting up WPML on your site, you noticed that certain admin menu items such as WPML->Languages and WPML->Translation Dashboard are missing.
Solution:
If you're experiencing this issue, it might be due to a problem with your database where the primary key isn't set to auto-increment properly. We recommend you to:
1. Access your website's database.
2. Ensure you have a complete backup of the database before proceeding.
3. Execute the following SQL commands:

DELETE FROM qpgw_term_taxonomy WHERE term_taxonomy_id = 0;

ALTER TABLE qpgw_term_taxonomy CHANGE COLUMN term_taxonomy_id term_taxonomy_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT;

These steps are crucial and should only be performed after ensuring that you have a complete backup of your database.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.

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 0 reply, has 1 voice.

Last updated by gregaV-2 3 months ago.

Assisted by: Christopher Amirian.

Author	Posts
March 4, 2025 at 12:40 pm #16773597
gregaV-2	Background of the issue: We are trying to finish the setup of WPML on our site hidden link. We are following the Getting Started Guide and WooCommerce Multilingual setup documentation. Symptoms: WPML->Languages is missing. WPML-> Translation Dashoboard is missing Questions: WPML admin menu items are missing?
March 4, 2025 at 1:08 pm #16774235
gregaV-2	Dabug information says the sql version is not as recommended. I do not understand why. The SQL server info is in the uploaded file.
March 5, 2025 at 7:15 am #16776695
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Welcome to WPML support. It seems that the WPML String Translation plugin is missing from your setup. - IMPORTANT STEP! Create a backup of your website. Or better approach will be to test this on a copy/staging version of the website to avoid any disruption of a live website. - Go to "WordPress Dashboard > Plugins > Add new > Commercial (tab)". - Click the "Check for Updates" button. - Install the WPML String Translation plugin See if it fixes the issue. Thanks.
March 5, 2025 at 12:11 pm #16778368
gregaV-2	Hi, String translation plugin was istalled (version 3.3.1). I have deleted the plugin and tried reinstalling, but it did not helped.
March 6, 2025 at 1:11 pm #16783402
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Thank you. I'd appreciate it if you could give me the URL/User/Pass of your WordPress dashboard after you make sure that you have a backup of your website. It is absolutely important that you give us a guarantee that you have a backup so if something happens you will have a point of restore. Make sure you set the next reply as private. Thanks.
March 9, 2025 at 8:16 am #16792456
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Thank you for login information. I followed the normal steps to install and setup, along the Woocommerce Multilingual setup there showed a critical error. I tried to login via FTP connection but the information doe snot work. Would you please follow the steps below to enable tehg debug mode to see what is the error under the hood? Would you please access your website files and edit the "wp-config.php" file on the root folder of your WordPress installation and add the code below into the file: define( 'WP_DEBUG', true ); define( 'WP_DEBUG_LOG', true ); define( 'WP_DEBUG_DISPLAY', true ); Please add the code above the line below: /* That's all, stop editing! Happy blogging. */ For more information: https://wpml.org/documentation/support/debugging-wpml/ Also get back to us with working FTP connection details by setting the next reply as private so that we can follow up. Thank you.
March 10, 2025 at 3:10 pm #16797292
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Thank you for the information. Unfortunately I could not access FTP anyways. Is there a limitation for the countries that can access the server? I used TLS as you mentioned. For now would you please go to wp-content/plugins and rename the sitepress-multilingual-cms folder to something else? That will force WPML to deactivate and I should be able to access the admin
March 11, 2025 at 10:50 am #16800922
gregaV-2	I have renamed the plugin so the page is error free. Yes IP limitation is for other countyes on port 21. go for port 6021, sorry for that.
March 12, 2025 at 2:49 pm #16807799
Christopher Amirian WPML Supporter since 07/2020 Languages: English (English ) Timezone: Asia/Yerevan (GMT+04:00)	Hi, Thank you for you patience. This error usually means that the table’s primary key isn’t set up to auto-increment properly. In a standard WordPress installation, the table (usually named something like wp_term_taxonomy) has a primary key column (typically called term_taxonomy_id) defined as an auto-incrementing field. When a new row is inserted without an explicit primary key value, MySQL should automatically assign the next available value. Instead, it’s trying to insert a default value (in this case, 0), which causes a duplicate entry error if a record with that key already exists. To fix the issue please access your website Database. Have a complete backup of the database. perform the SQL command below: DELETE FROM qpgw_term_taxonomy WHERE term_taxonomy_id = 0; And after that execute this SQL command: ALTER TABLE qpgw_term_taxonomy CHANGE COLUMN term_taxonomy_id term_taxonomy_id BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT; We can not stress enough that the steps above needs to be done after you have a complete* backup of the database.* Thank you.
March 13, 2025 at 9:42 am #16810856
gregaV-2	Ok, thank you for your quick support. This SQL has fixed the isue on stage and than live site. Kind regards!