Problem: You are trying to display order details on the 'Thank You' page at the final step of a purchase, but the order details do not appear on the translated language page, although they appear correctly on the main language page. Solution: We recommend updating to the latest version of WCML, specifically v5.5.3.1, which includes a fix for the order-received endpoint. Before updating, please ensure you take a full site backup. Also, update all WPML plugins to their latest versions to ensure compatibility and functionality.
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 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: After upgrading WPML to version 4.8.6, the client's test websites experienced toggling between the English and Dutch pages until an NS_ERROR_REDIRECT_LOOP was reported in the browser, indicating that the page isn’t redirecting properly. Solution: We recommended creating a staging environment of the website and running it with a minimal setup to determine if the problem persists. The client should: 1) Update WordPress to version 6.9. 2) Deactivate all additional plugins not related to WPML and our add-ons to see if the issue still occurs. If it does, we will attempt to replicate it on a test site. 3) If the problem disappears, gradually reactivate the plugins one by one or in small groups to identify the plugin causing the issue.
If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, 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 WPML support forum for further assistance.
Problem: The client reported that after translating a property into Greek, the content was missing on the Greek page. Additionally, some fields were still untranslatable. Solution: We advised the client to ensure that the ACF Field Groups were set to 'Not Translatable' in WPML → Settings → Post Types Translation. Then, in ACF → Field Groups → Property Fields, we recommended using the option to apply all fields across languages. For finer control, we suggested switching to 'EXPERT' mode to access field-level options. To address the missing content on the Greek page, the following steps were taken: 1. Edited the property in the default language. 2. Switched to Greek using the language switcher. 3. Scrolled to Theme/Page Options and copied the same settings from English to Greek, ensuring the Content Layout → Post Template was set. 4. Set the custom field 'thegem_page_data' to copy. For the untranslatable fields, we set the specific field 'ammenities' to 'Translate' in ACF Field Groups under 'Expert' mode and updated both the property and its translation.
If this solution does not resolve your issue, 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 problems persist, please open a new support ticket.
Problem: The client was experiencing issues with menu item links and labels not updating correctly in the Spanish version of their site. Specifically, the link for 'Recetas' was incorrect, and the footer label 'Guarniciones' was not updating to 'Extras' despite being translated. Solution: The client resolved the issue by editing the menu items to different values, then translating them, and finally restoring the original English values and retranslating. This process seemed to trigger a cache refresh which resolved the issue. Additionally, the WPML support team had suggested verifying and updating translations via WPML → String Translation, synchronizing menus through WPML → WP Menus Sync, clearing site and browser cache, and checking server requirements including increasing the WP_MEMORY_LIMIT.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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. For further assistance, please visit our support forum at WPML support forum.
Problem: After updating to version 5.5.3, you are encountering a fatal error on the payment page when making a payment in a language different from the original. The error is related to the 'woo-stripe-payment' plugin where it fails to get the currency from an order object, which turns out to be false. Solution: If the issue persists, try disabling and re-enabling your theme, as this approach resolved the issue. Additionally, ensure that your theme and all plugins are updated to their latest versions.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/ and verify the version of the permanent fix. If necessary, do not hesitate to open a new support ticket for personalized assistance.
Problem: The client needed to translate the default value of a hidden text field in an Elementor sign-up form but couldn't find relevant documentation. Solution: We recommended following the steps outlined in a specific WPML forum thread which discusses similar issues with Elementor forms. You can find the thread here: https://wpml.org/forums/topic/elementor-form-not-translated/#post-15079461. If the problem persists, we advised the client to provide temporary access to their site for further investigation. We also emphasized the importance of backing up the database and website before making any changes.
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 remains unresolved, please open a new support ticket at WPML support forum.
Problem: You are trying to translate a test page built with Elementor and encountering issues: The Image Box title remains in French across all languages. Solution: For the Image Box title not translating, we provided a workaround: 1. Backup your site. 2. Edit the functions.php file of your theme. 3. Add the following function:
4. Save the file. You might need to update existing translations for the fix to take effect.
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 needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client is trying to manually translate pages using WPML on a WordPress site without an SSL certificate. The issue is that the two-column translation view for the homepage shows incorrect content from a test Divi page instead of the default page content. Solution: The content appearing incorrectly in the translation view is due to a Global Body Template assigned to the 'Homepage' condition in the Divi Theme Builder. To resolve this, the client needs to manage the global Divi template through WPML → Translation Management.
If this solution does not apply to your case, or if it seems 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 WPML support forum.
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 issues with BuddyBoss profile fields not displaying their French translations in the app, despite the translations being visible in the WPML String Translation interface. Solution: 1. Ensure that BuddyBoss profile fields are registered for translation. This can be done from the BuddyBoss → Profile Fields section in the WordPress dashboard. 2. If the issue persists, it may be due to a conflict with a third-party plugin. We recommend: - Cloning the site to a staging environment. - Deactivating plugins one by one to identify the conflicting plugin. - Testing the translation again using the String Translation interface after each deactivation. 3. If you are unable to identify the conflicting plugin, consider backing up your site, switching to maintenance mode, and deactivating all third-party plugins temporarily to test the translations.
If these steps do not resolve your issue or if the solution 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 persists, please open a new support ticket at WPML support forum for further assistance.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
