Problem: You have a shop set up in Danish and have translated the shop page to English using WPML. While the shop page displays prices and categories correctly, the product titles appear in Danish instead of English. However, clicking on a product displays it in the correct language. Solution: First, ensure that your WPML and other related plugins are up to date. You can do this by navigating to your WordPress admin area, going to
wp-admin/plugin-install.php?tab=commercial
, and clicking on "Check for updates". After updating, verify if the issue persists. Next, check if the products showing Danish titles are drafts. If they are, you need to publish these products and ensure that their titles are translated correctly into English.
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 continue, please open a new support ticket.
Problem: If you're experiencing issues with translating the string "Recently Viewed Products" in the Astra theme or its addon plugin, follow these steps. Solution: First, navigate to WPML > Theme and plugins localization and select 'Scan strings in the theme and plugins'. After scanning, go to WPML > String Translation and search for the strings you need to translate. If you can't find the string "Recently Viewed Products", ensure you are searching under the domain "astra-addon". Once you find the string, translate it accordingly. For more detailed guidance, refer to our documentation on finding strings that don't appear on the String Translation page.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing a critical error (white page) when editing a post with WPML activated, and WPML indicates that the REST API is not activated even though it is working, the issue might be related to the ACF Multilingual plugin. Solution: We recommend reinstalling the ACF Multilingual plugin with a fresh copy. You can download it from here.
If this solution does not apply to your case, or if it seems outdated, 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. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
Problem: The client was experiencing an issue where clicking the Slovak flag on their website redirected to an incorrect URL instead of switching back to the Slovak version of the site. Solution: We recommended the following steps to diagnose and potentially resolve the issue: 1. Clear Cache: We advised clearing WPML’s internal cache from WPML > Support > Troubleshooting > Clear the cache in WPML, disabling the Language Switcher Cache, clearing any site caching plugins, and the CDN cache if applicable. 2. Use Footer Language Switcher: We suggested activating a footer language switcher from WPML > Languages to check if the issue persists with a different switcher setup. 3. Test in Minimal Environment: We recommended deactivating all plugins except WPML CMS and switching temporarily to a default WordPress theme like Twenty Twenty-one to see if the issue still occurs. This helps in identifying any conflicts with other plugins or themes.
Ultimately, the client discovered that the issue was caused by incorrect custom codes provided by their hosting service for redirecting www/non-www URLs in the wp-config file. Removing these codes resolved the problem.
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 issues persist, please open a new support ticket.
Problem: You are experiencing a 404 error on translated product pages after translating your website into multiple languages using WPML. Additionally, some necessary WooCommerce pages have not been created. Solution: First, ensure that the URLs for your translated pages do not contain special characters. For example, instead of using 'é', use 'e'. Here is a corrected URL that should work: https://sinotrukparts.com/fr/categorie-produit/pieces-detachees-howo/pieces-de-essieu-howo/ Second, verify that all necessary WooCommerce pages are created and properly configured in each language. If you're still facing issues, 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 solution provided here does not resolve your issue or seems irrelevant, please do not hesitate to open a new support ticket. We highly recommend visiting our support forum for further assistance: WPML Support Forum.
Problem: If you're experiencing issues with adding linked or cross-sell products on your product page while using the WPML String plugin, where typing the product name shows 'product not found', and deactivating the plugin resolves the issue. Solution: We recommend checking for any SSL misconfiguration on your site. This issue can prevent pages from fully loading, affecting the functionality of the WPML String plugin. Ensure that all resources, such as fonts and images, load over HTTPS instead of HTTP. You can verify this by inspecting your browser’s JavaScript console for any 'Mixed Content' warnings. If you find such warnings, resolving these SSL issues might fix the problem with adding products.
If this solution does not apply because it is outdated or not relevant 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 open a new support ticket.
Problem: You are encountering an error message related to the String Translation table on your site, specifically involving the 'wpml_string_table_ok_for_mo_import' key in the '_options' database table. Solution: First, delete the 'wpml_string_table_ok_for_mo_import' option from your database to hide the notice. Next, navigate to the WPML → Languages page. This action should automatically recreate the option. If your WPML tables are correct, this should resolve the message. However, if the error persists, it indicates that further database patching might be necessary. Please ensure to back up your database before making any changes.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is using WPML to create a Spanish version of their website and has encountered an issue where Spanish Memberships include English subscriptions. This prevents Spanish speakers from accessing content they purchased because the memberships do not recognize the Spanish subscriptions. Solution: We confirmed that the WooCommerce Memberships plugin is compatible with WPML. However, there are known issues that might be causing the problem described. We recommend checking the specific errata related to WooCommerce Memberships not assigning membership when purchasing a product in a secondary language. Here is the link to the errata: https://wpml.org/errata/woocommerce-memberships-does-not-assign-membership-when-purchasing-a-product-in-a-secondary-language/ Applying the suggested workaround from this errata may resolve the issue.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to register their site with WPML due to a site key not matching, despite previous successful registrations. Solution: We recommend checking if different URLs are being used for the home and main URLs. You should generate a WPML key for each URL version, as this might resolve the issue. If you're experiencing this, you can find a helpful screenshot in our support forum or directly view the image here.
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 experiencing an issue where a section of their website is not displaying in English as expected, despite previously showing correctly. This problem is occurring on the page: https://www.rezisieriai.lt/en/about/. Additionally, there is a separate issue where a translated logo is not showing correctly on the same page. Solution: We have identified that the issue with the section not translating might be related to a bug in BeTheme, not WPML, as the problem persists even when WPML is disabled. We recommend checking with BeTheme support to resolve this issue in the default language first. If the problem continues to occur only in the translated version after fixing it with BeTheme, please contact us again. For the issue with the translated logo not displaying, please refer to the existing support ticket here: https://wpml.org/forums/topic/translated-logo-stopped-showing-in-1-page/
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 issues persist, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where many string translations have disappeared from your site. This problem occurred without any updates being made initially, but persisted even after updating and scanning for new translations. Solution: First, ensure that you update WooCommerce and WPML to the latest versions as a recent issue with WordPress 6.7 could be affecting your translations. You can learn more about this specific issue here: WPML Errata. Next, go to WPML > Theme and plugins localization and select the option to 'Automatically load the theme's .mo file using
load_textdomain
'. This adjustment has resolved the issue for other clients experiencing similar problems.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: You are trying to display a translation for a global section on your website, but it is still showing in the original language. The translation for the global section is not appearing as expected, displaying in Lithuanian instead of English. Solution: 1. Ensure that you go to BeTheme → Theme Options → Global → Advanced and set the value of the Muffin Builder data storage to
"Serialized | Readable format"
, which is required by some plugins. 2. If you are using Templates, make sure that they are translated. 3. Set the following custom fields to "copy": - mfn_footer_template - mfn_header_template 4. Edit the original footer, save it, and apply the translation again. For more detailed guidance on translating custom fields, please visit: Translating Custom Fields Documentation
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 is unable to translate widget titles on their website using WPML, despite having encountered and resolved a similar issue previously. Solution: 1) In WPML String Translation, scroll to the bottom and click on the Translate texts in admin screens link. Search for the widget title, add it for translation, and then translate it. 2) Alternatively, consider adding two widgets, one for each language (GR and EN), with their respective translated titles. This method is detailed in our documentation: Translating Widgets.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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: The client is facing two issues: unable to use 60000 credits for automatic translation and encountering an error when switching from Greek to English related to the function
_load_textdomain_just_in_time
. The error indicates that the translation loading was triggered too early. Solution: 1) The error related to
_load_textdomain_just_in_time
is a known issue in WordPress and not specific to WPML. It can occur even if WPML is disabled. For more details, please visit WPML Errata. 2) To address the issue with using credits for automatic translation: - Navigate to WPML > Support > Troubleshooting. - Click on "Synchronize local job ids with ATE jobs" and "Synchronize translators and translation managers with ATE". - Resend the page for translation from WPML > Translation Management. - Go to WPML > Translation, take and translate the job.
If these steps do not resolve your issues or if the solution seems outdated or irrelevant 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 the problem persists, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing an issue where translated strings only display when the 'Look for strings while pages are rendered' option is enabled, following a recent WordPress update. Solution: If this issue occurred after updating to WordPress 6.7, we recommend you check the following documentation on missing translations on the front end: https://wpml.org/errata/missing-translations-on-front-end/. Downgrading WordPress to the prior version might be an option as workaround. If this does not apply to your case, please contact us for further investigation.
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, do not hesitate to open a new support ticket for personalized assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
