Problem: The client is experiencing issues with the qtranslate importer plugin on a site with three languages: Traditional Chinese (default), Simplified Chinese, and English. The Traditional Chinese language is not being recognized correctly, resulting in only two languages appearing in the WPML settings, and the menu not being converted. Solution: 1) Check the language codes used by QTranslate and WPML. Before activating WPML and starting the import process, verify the language codes in QTranslate and then in WPML. If they differ, add a custom language in WPML with the same language code used by QTranslate. For instance, WPML uses the standard codes 'zh-hans' for Simplified Chinese and 'zh-hant' for Traditional Chinese. 2) If the menu is not converting, it might be necessary to manually create the menu in the default language and then translate it.
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. Additionally, 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, visit our support forum at WPML Support Forum.
Problem: You are encountering an authentication issue when trying to interact with our API, even after re-registering your access key and increasing the memory limit to 256M. Solution: We recommend going to WPML > Settings > Translation Editor and re-enabling the Advanced Translation Editor (ATE) by saving the changes. This should allow you to translate the content on your site using ATE.
If this solution 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 further assistance is needed, please open a new support ticket at our support forum.
Problem: If you're experiencing an error every time you try to activate WPML, it might be due to a compatibility issue with another plugin on your site. Solution: We recommend deactivating the "Share Buttons by AddThis" plugin and then trying to activate WPML again. This plugin is known to cause issues with WPML as it is not currently listed in our compatible plugins directory. If deactivating the plugin resolves the issue, you might consider contacting the plugin's author to encourage them to join our Go Global program where we help developers make their plugins compatible with WPML. You can find more information about this program here: https://wpml.org/documentation/support/go-global-program/
If this solution 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 problems persist, please open a new support ticket with us for further assistance.
Problem: When WPML String Translation is activated, the Japanese version of the Woocommerce cart leads to a 404 error page. Disabling WPML String Translation allows the cart to be visible, but some pages do not display information correctly. Solution: If you're experiencing this issue, we recommend you try the following steps: - Go to WPML -> Settings -> Post Types Translation -> Products (product) - Click on 'Set different slugs in different languages for Products' and ensure that the slug for the Japanese version matches those of other languages, such as setting it to 'tienda' to align with the Spanish and English versions. After these adjustments, the Japanese cart page should start loading correctly.
Please note that 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.
Problem: The client is unable to translate a page from English to Italian using WPML. The translation is stuck in progress, showing only a cog icon instead of the + icon, indicating that the translation cannot be edited because it is already in progress. Additionally, attempts to cancel the translation job through WPML result in an error stating that the action does not apply to any of the selected translation jobs. Solution: 1. Contact Transifex and request them to cancel the translation job on their end. 2. Navigate to WPML > Translation Management > Translators. Under 'Translation Services', deactivate the Transifex connection. 3. Attempt to translate the page again. If the issue persists, visit WPML > Support > Troubleshooting and click on Reset professional translation state to ensure no professional translations are stuck in progress.
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. Additionally, 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 WPML support forum.
Problem: The client was experiencing an issue where the translated homepage appeared white and was not displaying correctly after using translation credits. Additionally, there were PHP deprecation warnings related to the WPML Sticky Links plugin. Solution: We first suggested enabling WP_DEBUG in the wp-config.php file to identify any fatal errors causing the white page issue. Instructions for enabling debugging can be found here: https://wpml.org/documentation/support/debugging-wpml/. After reviewing the error logs and finding no fatal errors, we advised the client to change the Language URL format in WPML settings to 'Language name added as a parameter' and check if the issue persists. We also recommended ensuring that WordPress is not installed in a directory with a conflicting 'en' folder.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problem continues, please open a new support ticket at WPML support forum for further assistance.
Problem: You are working on a site under development and have added a plugin in the widgets. While you can translate some strings using WPML, others remain untranslated. Solution: First, ensure you back up your site. Then, add the following code to your
// WPMl Workaround for compsupp-7428
function wpml_compsupp7428_register_and_translate_labels_for_wooVPF($label) {
if (class_exists('Sitepress')) {
$string = $label;
$textdomain = ' woo_vpf_ymm'; // Replace with your actual text domain
$string_name = 'Woo VFP: ' . substr($string, 0, 20);
if (apply_filters('wpml_default_language', NULL) == apply_filters('wpml_current_language', NULL)) {
do_action('wpml_register_single_string', $textdomain, $string_name, $string);
}
// Apply the translation to the string
$label = apply_filters('wpml_translate_single_string', $string, $textdomain, $string_name);
}
return $label;
}
// List of filters to apply the custom function
$label_filters = [
'woo_vpf_ymm_year_label',
'woo_vpf_ymm_make_label',
'woo_vpf_ymm_model_label',
'woo_vpf_ymm_engine_label',
'woo_vpf_ymm_category_label',
'woo_vpf_ymm_keyword_label',
'widget_woo_vpf_ymm_label_year',
'widget_woo_vpf_ymm_label_make',
'widget_woo_vpf_ymm_label_model',
'widget_woo_vpf_ymm_label_engine',
'widget_woo_vpf_ymm_label_category',
'widget_woo_vpf_ymm_label_keyword',
'widget_woo_vpf_ymm_label_search',
'widget_woo_vpf_ymm_label_reset_search'
];
// Apply the custom function to each filter
foreach ($label_filters as $filter) {
add_filter($filter, 'wpml_compsupp7428_register_and_translate_labels_for_wooVPF');
}
After adding the code, follow these steps:
Go to the page with the strings in the original language to register it.
Navigate to WPML > String Translator and locate the strings.
Change the language of the strings from English to French.
Translate the strings to English.
If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to see translations for a specific widget in the language switcher, despite having translated the widget and other content. The widget content was only displaying in Greek, regardless of the selected language. Solution: We suggested several steps to resolve the issue: 1. Ensure that translations are not saved in 'Draft' mode and apply any pending translation reviews in bulk via WPML > Translations. 2. Assign the widgets to 'All languages' and use WPML > String Translation to translate them. More details can be found here: Translating Widgets Using String Translation 3. Increase the WordPress memory limit to at least 256MB by adding the following code to the wp-config.php file:
define ('WP_MEMORY_LIMIT', '256M');
This code should be placed just before the comment:
// That's all, stop editing! Happy blogging.
4. After increasing the memory limit, save the widget settings again and check if the issue is resolved.
If these steps do not resolve the issue or if the solution becomes outdated, we 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The "AREA RISERVATA" from "Full Menu" shows untranslated in the Front End due to a compatibility issue with dynamic fields from the Lottie widget. Solution: If you're experiencing this issue, we recommend creating a full website backup first. Then, add the following code to your functions.php file:
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.
Problem: The client is unable to find specific messages for translation in the WPML string translation interface. These messages appear on a form when a required checkbox is not marked and after form submission, using the Dynamic.ooo plugin with Elementor. Solution: We suggested isolating the issue to determine if it's caused by the site's configuration or the combination of the Dynamic.ooo plugin and WPML. We provided a sandbox environment for the client to replicate the issue: 1. Access the sandbox link. 2. Download and activate Elementor and the Dynamic.ooo plugin. 3. Create a basic form on a page with a required checkbox similar to the one on the client's site. 4. Translate the page and save the changes. Check if the issue replicates in this controlled environment. For more details on reproducing issues, visit https://wpml.org/faq/how-to-reproduce-issues-and-share-them-with-wpml-support/.
If this solution does not apply because it might be outdated or not relevant to your case, we recommend opening a new support ticket. We also 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.
Problem: You are trying to import posts via an XML file using WP All Import and WPML All Import, and the posts should be linked to each other based on the same ID. However, some imported posts are not linked despite having the same ID. Solution: We recommend checking the following guides to ensure you are following the correct steps:
The imported file should have an identifier to connect the two languages.
If this solution 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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client wants to change the language code for Chinese simplified and Portuguese Portugal without affecting the existing content Solution: We recommend creating a new custom language with the desired language code instead of changing the existing one, as altering the language code directly in the database could break your site. For Chinese, you can create a language with the code 'ZH'. Please refer to our documentation on editing WPML's languages table and watch this helpful video: video guide. For the existing translated content in 'zh-hans' or 'pt-pt', you can duplicate them in bulk to the new languages using the WPML Translation Management Dashboard. For more details, check out how to duplicate pages and posts in bulk.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: You are setting up a language switcher using WPML on your site under development, but the flags are not showing. Solution: The issue might be due to the missing "wp_icl_flags" database table. Here's how you can address this: 1. Ensure you back up your site first for safety. 2. Insert the following code at the bottom of the functions.php file in your theme's root folder:
3. After adding the code, visit your site's homepage at least once. 4. Remove the code afterward. If the problem persists, we may need to install the wp phpMyAdmin plugin on your site to add the missing database table.
Please note that this solution might be 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 continues, please open a new support ticket.
Problem: You are trying to display posts on your blog page in the translated version of your site, but the blog page does not display the posts in the translated version. Solution: We found that the issue was due to certain admin strings being incorrectly translated. Specifically, the strings that caused the issue are:
[theme_mods_tripgo-child]blog_template
page_for_posts
[sidebars_widgets]
Please ensure these strings are not translated in the WPML String Translation section. If you're experiencing this issue, we recommend checking these strings.
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 problem persists, please open a new support ticket.
Problem: You are using Advanced Translator to translate a page and encounter an issue where fields containing code elements are converted to "wmpl_curved" elements, and you cannot save these fields, preventing the completion of the page translation.
Solution: It was a temporary issue which our ATE/Dev teams fixed swiftly and has already been rolled out. If you're still experiencing, please clear cache, cancel an existing job and retry.
If this solution becomes irrelevant due to updates or does not apply to your case, we recommend opening a new support ticket. We also advise 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.
For further assistance, please visit our support forum at WPML Support Forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
