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.
Problem: You have translated your footer into Turkish, but the Turkish page still displays the English footer. Additionally, when attempting to change it, an error message appears. Solution: We reviewed your site via WPML -> Translation Management and confirmed that the Turkish translation of the footer is correct. However, it seems that the translated footer is not loading on the front end. This issue might be due to the footer template being linked to a specific post ID that has not been updated to the translated version. In Elementor, ensure that the footer is defined correctly in the "Theme Builder" section. Since you are using the free version of Elementor, some options might be restricted.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Also, check the related 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, please visit our support forum.
Problem: You have successfully translated ACF custom fields, but they do not appear on the translated pages. Solution: We recommend installing the Advanced Custom Fields Multilingual (ACFML) plugin to ensure that your translated custom fields appear correctly on translated pages. For detailed guidance on installing and configuring ACFML, please visit this documentation.
If the solution provided here does not resolve your issue or 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 at WPML support forum.
Problem: You are experiencing issues with sorting products by price in descending order on your site after translating products from Chinese to English using WPML. The sorting works correctly in the Chinese version but not in the English version. Solution: We recommend following these steps to resolve the sorting issue: 1. Increase the WP Memory Limit. For more details, check this link: WPML Minimum Requirements 2. Enable a minimal environment: - Deactivate all plugins except for WPML plugins and WooCommerce. - Switch to a standard WordPress theme. IMPORTANT: Please backup your database and website before proceeding. 3. Bulk edit translation products and re-update them without changes. For more information, visit: Bulk Update Products
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 WPML 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: You have installed WPML and translated your front page, but when trying to open or edit the translated version, you receive a critical error. The error logs indicate an issue with the 'Add Any Extension to Pages' plugin, which is not compatible with WPML. Solution: We recommend deactivating the 'Add Any Extension to Pages' plugin to resolve the critical error. This plugin is not currently on WPML's list of compatible plugins, and its compatibility with WPML cannot be guaranteed. You can check the compatibility of plugins with WPML here. If the issue persists after deactivating the plugin, consider contacting the support team of 'Add Any Extension to Pages' for further assistance. Additionally, you can suggest that they join the Go Global program to make their plugin compatible with WPML. More details about the program can be found here.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues here, 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 here.
Problem: The client is using the wpresidence theme, translating from English to Arabic. They encountered issues where the design and block positions differ between the two languages. Changes in the English version caused problems in the Arabic version, including misalignment and incorrect display of elements such as the floor plan size. Solution: We recommended CSS adjustments to address RTL (Right-to-Left) support issues and alignment problems. For example:
For translating strings like 'Resale', 'Rentals', and 'Projects', use the WPML String Translation tool. If strings are not found, follow the guide at this guide. For issues not resolved by these steps or if the solution 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 problems persist, please open a new support ticket 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
