Problem: The client encountered a PHP Fatal error on the Translations Jobs tab, indicating an issue with calling a function on a boolean value in the WPML plugin code. Solution: We resolved the issue by repairing the corrupted WPML tables in the database. We executed a series of SQL queries to alter the tables and set the correct auto-increment values. Here are the queries we used:
ALTER TABLE `wp_icl_translation_batches`
CHANGE `id` `id` int(11) NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_translate_job`
CHANGE `job_id` `job_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_translate`
CHANGE `tid` `tid` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
DELETE FROM `wp_icl_strings`
WHERE ((`id` = '0'));
ALTER TABLE `wp_icl_strings`
CHANGE `id` `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_string_batches`
CHANGE `id` `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_string_packages`
CHANGE `ID` `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_string_positions`
CHANGE `id` `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_string_translations`
CHANGE `id` `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_string_status`
CHANGE `id` `id` bigint(20) unsigned NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_languages_translations`
CHANGE `id` `id` int(11) NOT NULL AUTO_INCREMENT FIRST;
ALTER TABLE `wp_icl_languages`
CHANGE `id` `id` int(11) NOT NULL AUTO_INCREMENT FIRST;
... (and similar queries for other WPML tables). We asked the client to check if the issue was resolved after applying these changes.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.
Problem: The client allocated 6000 credits to their staging site but received a message indicating no credits were available when trying to translate content. Additionally, they encountered a 'critical error' message when attempting to translate certain pages.
Solution: 1. We assigned 10k credits to the client's automatic translation account, which they should now see in the top left area of their WPML Translation Management page.
2. We advised the client to move the original 6000 credits back to their WPML.org account by clicking the blue "add/remove credits" button on their WPML account downloads page.
3. We instructed the client to remove the current site key from their WPML account, generate a new one, unregister WPML from the old key, and re-register WPML with the new key on their website. This process is to re-establish the connection between the website and a new clean automatic translation account.
4. For the 'critical error' issue, we recommended checking server configuration and compatibility with WPML's minimum requirements, activating WordPress debug, and testing for plugin or theme conflicts by deactivating all non-WPML plugins and switching to a default WordPress theme.
If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable to your 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 you still need assistance, please open a new support ticket at our support forum.
Problem: The client is encountering a database error indicating a duplicate entry '0' for the primary key when trying to save a translation. This error suggests that AUTO INCREMENT may be deactivated on the database table.
Solution: 1. Check the
icl_translation_status
table in the database to ensure that AUTO INCREMENT is enabled. 2. If AUTO INCREMENT is not enabled, it needs to be activated. This may also require checking other WordPress tables like
wp_options
,
wp_posts
, and
wp_users
to ensure they have AUTO INCREMENT enabled where necessary. 3. If there is an entry with '0' in a table where you are trying to enable AUTO INCREMENT, you must remove that entry before you can enable AUTO INCREMENT. 4. Always ensure you have a recent and working backup before making any changes to the database.
Please note that this solution might not be relevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
