Problem: You are experiencing an issue where WPML is missing some records in the languages tables, which prevents it from fully working. Despite following the suggested troubleshooting steps like clearing language information and repopulating languages, removing ghost entries, fixing terms and taxonomy relationships, setting language information, assigning translation status to duplicated content, and fixing post type assignment for translations, the problem persists.
Solution: If you're facing this issue, we recommend you try the following steps after taking a database backup: 1- Open your database manager, for example, PhpMyAdmin. 2- Navigate to the "wp_options" table (note: 'wp_' is a standard prefix, yours might be different but the table name will be similar to xx_options). 3- Execute the following SQL query to search for the 'icl_admin_messages' key:
SELECT *
FROM `wp_options`
WHERE `option_name` LIKE '%icl_admin_messages%'
LIMIT 50;
4- Delete this key from your database. 5- Clear your cache, refresh your dashboard, and check if the message has disappeared.
This solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to translate the name of a product variation in a WooCommerce site using WPML. Despite the translation being completed in the Advanced Translation Editor (ATE), the variation name still displayed in the original language on the front-end.
Solution: We identified that the issue was related to a custom function in the theme's
functions.php
file, which incorrectly handled language information and prevented translations from being applied. We modified the function to ensure it checks for valid data before proceeding. Here's the corrected code snippet:
if (function_exists('wpml_get_language_information')) {<br /> $lang_info = wpml_get_language_information($post_id);<br /> // Check if we got a WP_Error<br /> if (is_wp_error($lang_info)) {<br /> error_log('WP_Error encountered in wpml_get_language_information: ' + $lang_info->get_error_message());<br /> return; // Stop execution if there's an error<br /> }<br /> <br /> if ($lang_info['language_code'] !== 'en') {<br /> return;<br /> }<br />}
After applying this fix, the product variation name displayed correctly in all languages. If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. We highly recommend opening a new support ticket if further assistance is needed. You can do so at WPML support forum.
Problem: The client is trying to auto-translate taxonomy terms for 'Amenities' in bulk, but cannot find the option in the WPML -> Translation Management filter dropdown. The client can see the terms in the manual translation section (WPML -> Taxonomy translation) but wants to translate all terms at once automatically, not one by one in all languages. The 'Amenities' taxonomy is already set as translatable in WPML -> Settings.
Solution: We recommend creating a single post that includes all the 'Amenities' taxonomy terms. Then, translate this post using the WPML Translation Editor, which will allow for bulk translation of all taxonomy terms. This method also enables the use of automatic translations. For a step-by-step guide, please refer to our documentation:
Please note that this solution might be outdated or not applicable to your case. If it doesn't resolve your issue, 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 you still need assistance, please open a new support ticket in our support forum.
