Problem: The client was unable to see the content in the text editor box inside the widget in the Advanced Translation Editor (ATE) when using WPML to translate the Filterable Gallery widget from the Essential Addon for Elementor. Solution: We identified an incorrect field definition in the WPML configuration XML. The client initially had
resolved the issue. Additionally, we suggested setting the
editor_type
to "LINE" for fields in the WPML config that are used with the Advanced Translation Editor, as the default is "LINE" and the only field set to "VISUAL" might not display correctly.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an Internal Server Error on the French version of your website after using WPML to translate from Arabic to English and French, the issue might not be with the .htaccess file itself. Solution: We recommend trying the workaround detailed in this documentation: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/. You should add the workaround to the
functions.php
file of your parent theme. However, to avoid losing this change during theme updates, we suggest switching to a child theme and adding the workaround there.
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 the problem persists, please open a new support ticket.
Problem: You are using the MEDIA translation plugin along with multilingual and multicurrency plugins, but they do not appear in the settings. Solution: We are aware of this issue and recommend that you ignore it for now. All WPML plugins will continue to function normally, and this should not affect your site. The fix for this issue will be included in one of our upcoming releases.
If this solution 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 the problem persists, please open a new support ticket at our support forum.
Problem: You are trying to display a translated global form using WPML on your Elementor site, but the form appears in the original English instead of the expected translation. Solution: This issue has been reported to Elementor and will be fixed in a future update of the plugin. In the meantime, we recommend adding the following code to your theme's functions.php file to ensure the Elementor global form is translated correctly. Please ensure you have a full backup of your site before proceeding.
// === WPML not translating contact forms FIX ===
if ( ! is_admin() ) {
add_filter( 'get_post_metadata', 'wpmlpb_735_translate_elementor_data', 10, 4 );
}
function wpmlpb_735_translate_elementor_data( $value, $object_id, $meta_key, $single ) {
// Only act on Elementor data
if ( '_elementor_data' !== $meta_key ) {
return $value;
}
// Temporarily remove this filter to avoid infinite recursion
remove_filter( 'get_post_metadata', 'wpmlpb_735_translate_elementor_data', 10 );
// Get the actual Elementor data
$elementor_data = get_post_meta( $object_id, '_elementor_data', $single );
// Re-add the filter
add_filter( 'get_post_metadata', 'wpmlpb_735_translate_elementor_data', 10, 4 );
// Process and convert dynamic elements if possible
if ( is_string( $elementor_data ) && ! empty( $elementor_data ) ) {
$data_array = json_decode( $elementor_data, true );
if ( is_array( $data_array ) && class_exists( '\WPML\PB\Elementor\Hooks\DynamicElements' ) ) {
$dynamic_elements = new \WPML\PB\Elementor\Hooks\DynamicElements();
$data_array = $dynamic_elements->convert( $data_array );
return json_encode( $data_array );
}
}
return $elementor_data;
}
Test this solution on a staging site first. If you encounter any issues or need further assistance, please do not hesitate to contact us. Additionally, 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 this solution does not apply or is outdated, please open a new support ticket.
Problem: You are trying to translate custom fields in the Houzez theme for a property listing website using WPML. The issue is that when creating a property in Arabic and trying to edit it from the backend, the custom fields are written in English, and the values of these fields are stored in English in the database. This results in no search results when searching for a property in Arabic using the custom field with its Arabic value. Solution: First, ensure that the custom select field is set as "COPY" to keep the same value in the property translation and that the custom select field labels are translated in String Translation. Then, modify the code in the
This modification keeps the value of the field untranslated but translates the label, ensuring correct functionality in both languages.
If this solution 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 the problem persists, please open a new support ticket.
Problem: After a recent WPML update, you are unable to manually translate products in WooCommerce. When attempting to translate, you encounter an error stating 'The translator could not be assigned to the job,' and you are redirected to the 'translation queue' page instead of the product edit page. Solution: This issue is due to missing fields in the database table wp_icl_translate_job. To resolve this, please ensure you back up your entire server first for safety. Then, run the following database query to add the necessary fields:
ALTER TABLE `wp_icl_translate_job`
ADD `wpml_words_to_translate_count` int unsigned NULL,
ADD `wpml_automatic_translation_costs` int unsigned NULL AFTER `wpml_words_to_translate_count`;
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking for 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. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance.
Problem: You are experiencing a fatal error after attempting to update WPML Multilingual CMS & WPML String Translation. The error logs indicate a PHP Fatal error due to 'Too few arguments to function WPML_ST_Slug_Translations::__construct()'. Solution: We recommend creating a full backup of your site before proceeding with any further actions. The likely cause of the fatal error is that not all plugin files were copied correctly during the update. If the error persists after checking and ensuring all files are correctly updated, please contact us for further assistance. We may need to request access to your site to investigate further and identify the exact cause.
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 continues, do not hesitate to open a new support ticket at WPML support forum.
Problem: After migrating to a new server, you might find that your multilingual domain setup with WPML's 'Different domain per language' option is not working correctly for bare domains (without www). For instance, accessing https://heatperformance.no redirects to https://www.heatperformance.nl instead of loading the correct language site. Solution: This behavior is expected because WPML relies on the WordPress Home/Site-URL settings, which are configured to include 'www'. Therefore, any redirection for bare domains needs to be manually set up in your .htaccess file. For more detailed guidance on configuring these redirects, please visit WPML forum topic on domain redirection.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, it's advisable to check related known issues at WPML 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 WPML Support Forum.
Problem: The client is experiencing persistent 500 errors linked to WPML on their staging site, despite extensive troubleshooting including deactivating less essential plugins, reverting to older WPML versions, and consulting forum topics. The errors persist even after enabling WordPress debugging and updating plugins.
Solution: We recommended the following steps to further diagnose and potentially resolve the issue: 1. Enable WordPress debugging to capture specific error messages. This involves adding specific lines of code to the
wp-config.php
file to log errors without displaying them on the site. 2. Reproduce the error to trigger and log specific error messages, then share these messages for further analysis. 3. Ensure all WPML components are updated to the latest versions after ensuring a complete backup of the site and database. 4. If the issue persists, we advised checking the PHP memory limit and using WPML’s troubleshooting tools.
If these steps do not resolve the issue or if the solution becomes outdated, 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. For further assistance, please visit our support forum at https://wpml.org/forums/.
Problem: The client modified the brand page layout to support a specific URL structure and used WPML for multilingual support on their WordPress site. While the filters worked correctly in the English version, the product filters (Filter Products by Price, WOODMART Product Category Filter, and WOODMART WooCommerce Layered Nav) did not display on the Thai version of the site. Solution: We advised the client to ensure that the layout and the Elementor sidebar were translated and published with the correct conditions set in Thai. The client confirmed that the Thai layout was not auto-publishing after translation. After manually publishing the translated layout, the filters started working normally.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing a fatal error when activating the Turkish translation on their website using WPML String Translation. The error indicates missing interface bindings in the WPML core, specifically when the WP-Parsidate plugin is active. This issue causes the website to crash only when switching to the Turkish language. Solution: We investigated the issue by creating a copy of the client's website. We identified that the conflict was with the WP-Parsidate plugin. Deactivating the WP-Parsidate plugin resolved the fatal error, and the Turkish language started to function correctly on the site. For more details, you can watch this video: https://kommodo.ai/recordings/NuCO9LutwYYa95HrJ28o
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to manually translate a page but encounter a white screen and errors in DevTools after pressing the '+' button. Solution: We recommend you try the following steps to resolve the issue: 1. Clear your browser cache. 2. Test using a different browser. 3. Temporarily disable any browser extensions, such as ad-blockers, and try again. These steps might help if the issue is related to local browser settings or extensions interfering with the WPML functionality. If the problem persists, it could be a temporary server issue.
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 continues, please open a new support ticket at our support forum.
Problem: You are trying to translate shortcode contents on your site using WPML, but the translations are not being applied. Specifically, shortcodes like 'tatsu_toggle' and 'tatsu_button' are not displaying the translated content on your German site, despite being visible and translatable in the WPML Translation Editor. Solution: The root of the issue is that the Tatsu page builder and other Brand Exponents products are not compatible with WPML. Therefore, they cannot be reliably translated using WPML’s Translation Editor. To resolve this, you should disable the WPML Translation Editor and translate your content manually using the page builder itself. You can follow this guide on how to switch to manual translation mode: Using Different Translation Editors for Different Pages. If you consider switching to a WPML-compatible builder in the future, you can check the full list of supported themes and plugins here: Theme Compatibility.
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 at WPML Support Forum.
Problem: The client is unable to see their account to assign themselves as a translator in WPML, despite being an admin. Solution: If you're experiencing this issue, we recommend the following steps: 1. Navigate to Products > All Products in your WordPress dashboard. 2. Click on "Screen options" at the top right of the screen and ensure that the "Language" option is enabled. 3. Look for translation icons next to each product in the list at Products > All Products, which allow direct access to translations. 4. Alternatively, you can access the translation editor directly from the right sidebar of the WordPress Editor while viewing the original product.
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.
Problem: You are trying to allow customers to choose different lengths for the 'monkey and giraffe' products on your product page. This functionality works correctly in Dutch and German, but in English, only one length option is visible instead of two. Solution: We recommend you follow these steps to resolve the issue: 1. Edit the product in the original language. 2. Navigate to Variations and open the specific length variation. 3. Temporarily reduce the stock quantity, save the changes, and update the product. 4. Restore the original stock quantity, save again, and update the product. These steps should help to correctly sync the variation with its translations. Try these steps for the 'giraffe' product as well.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
