Problem: The client is experiencing an issue where the WooCommerce 'order-received' page only displays correctly in the default language. In other languages, it shows a single sentence instead of the translated thank you page. Solution: We have resolved this issue, and it will be included in the upcoming WCML v5.5.3.1 release. We recommend updating all WPML plugins once the update is available to ensure that the 'order-received' endpoint functions correctly in all languages. Before proceeding with the update, please ensure to take a full site backup.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket.
Problem: The client is experiencing issues with WPML and Elementor Pro on their multilingual site. Specifically, translated pages are not applying Elementor templates correctly, and Forminator forms are not being detected by WPML for translation.
Solution: For the Elementor template issue, we recommend setting the '_cmsmasters_locations' custom field to 'Copy' at WPML > Settings > Custom Field Translation. Then, update the original template and re-translate using the WPML Translation Editor to ensure the template's location rule copies correctly. If issues persist, it may require compatibility adjustments from the theme or plugin developers. For more details, revise the last comment on this ticket.
For Forminator, as it lacks WPML integration, create separate forms for each language and manually use the shortcode on the respective pages. Consider scanning the plugin for strings at WPML > Theme & Plugin Localization and translating any detected strings at WPML > String Translation. Alternatively, explore other form plugins compatible with WPML, listed here: https://wpml.org/plugin-functionality/form/
If these solutions do not resolve the issues or seem 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 problems persist, please open a new support ticket at our support forum.
Problem: You are helping a client who owns a WPML Lifetime license but cannot access her WPML account. When trying to update WPML using the OTGS Installer, the Installer crashes with a PHP Fatal error. Despite deleting old WPML and Installer plugin folders, reinstalling the latest official OTGS Installer plugin, registering the site again, and clearing caches, the Installer still fails with the same fatal error. Solution: 1. First, ensure that the WordPress Memory Limit meets the minimum requirements. We recommend setting it to 256M. You can increase the memory limit by adding the following lines to your wp-config.php file, right before the /* That’s all, stop editing! Happy publishing. */ line:
After updating, confirm the change under WPML > Support > WordPress > Memory limit. 2. If you encounter an error stating "The uploaded file exceeds the upload_max_filesize directive in php.ini", contact your hosting provider to increase the PHP resources of your server.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing a critical error when attempting to use the advanced editor for translating a page from English to French. The error message indicates a missing site key and issues with the WPML Translation Editor, potentially due to conflicts with hidden builder metadata or cached layout data from Visual Composer. Solution: We recommend creating a new page and manually copying the content from the problematic page to the new one. This approach often helps clear out any residual builder metadata that might be causing the issue. If this solution does not resolve the problem or if it seems outdated or irrelevant to your current setup, please 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. If issues persist, we highly recommend opening a new support ticket for further assistance.
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 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: 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: 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 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: 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: The client is attempting to translate the XPro Multi Layer Slider content in a WordPress Multisite using WPML and Elementor. Despite adding custom XML configuration to WPML → Settings → Custom XML, the widget fields are not appearing for translation in the WPML editor. Solution: We investigated the issue by accessing the client's site and creating a test page with the slider. It was determined that the slides are pre-loaded with content from a template. To translate the slides, the client needs to manually edit the page in the secondary language using Elementor and select the correct slides. We provided a video demonstrating these steps: https://kommodo.ai/recordings/RXSgiCZlpz9H7wddVAVy
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. 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. For further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: You are encountering issues with the WPML plugin and the WPResidence theme, specifically with language display in the 'Lists by Category' column under the footer and a missing user type selection in registration forms. After clearing the cache, the language in the 'Lists by Category' column does not update across different languages. Additionally, the user type selection does not appear in the registration forms despite following suggested solutions. Solution: For the caching issue related to the 'Lists by Category' column, it appears to be a known issue with the WP Residence theme. We recommend checking the related known issue here: WP Residence Studio Templates Header/Footer Display in Wrong Language. For the registration form issue, our second-tier support has confirmed it as a bug. Please follow these steps: 1. Back up your website. 2. Open the
if (defined('ICL_LANGUAGE_CODE')) { $transient_key .= '_' . ICL_LANGUAGE_CODE; }
After making these changes, please recheck the functionality.
If this solution does not resolve your issues 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 issues persist, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the site logo is not appearing in the translated header and footer on their multilingual website. Solution: If you're facing a similar issue, we recommend following these steps: 1. Ensure you have a backup of your site. 2. Install and activate the WPML Media Translation plugin. You can install it via your WP dashboard under Plugins >> Add New Plugin > Commercial tab, or download it from here. 3. Navigate to WPML >> Media Translation. 4. Search for 'logo' and press the Filter button. 5. Click on the Plus (+) icon, add the logo name in the Name field to enable the save button, and then press the “Save media translation” button. 6. Clear all sorts of site/server/CDN cache. If the logo still does not appear, you might consider deactivating and deleting the WPML Media Translation plugin as it should continue to work. Alternatively, check the suggestions in this thread: WPML forum thread.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
