Problem: You are experiencing a 404 error on the homepage of your site when it is set to the English language. Solution: First, check if there is an /en folder where WordPress is installed. Next, navigate to WPML->Languages->Language URL format and switch to 'language as a parameter' URL format to see if the English page appears correctly. Additionally, 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/.
If these steps do not resolve the issue, it might be because the solution is 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with product variants disappearing after updating WooCommerce Multilingual & Multicurrency to version 5.3.9, it might be due to conflicts with other plugins or themes. Solution: We recommend the following steps to troubleshoot and resolve the issue: 1. Ensure that only WooCommerce, WPML, and our addons are enabled when updating to the latest version of WooCommerce Multilingual & Multicurrency. 2. If the issue persists, try enabling all plugins and the child theme again to check if the problem still does not occur. 3. On your live site, delete any minified files created by Assets Cleaner PRO and clear the site's cache before updating. 4. Check for configuration issues under WooCommerce > WooCommerce Multilingual & Multi-Currency > Status. 5. Go to WPML > Settings > Post Type Translation and set "Variations (product_variation)" to "Translatable - only show translated items" and save the settings. 6. In WPML > Settings > Custom Fields Translation, click "Show system fields" and set the field
_crosssell_ids
to "Translate". If these steps do not resolve the issue, the 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to translate certain strings in Gravity Forms using WPML on their website built with Beaver Builder. Specifically, strings like 'First', 'Last', 'Required', 'Enter Email', 'Confirm Email', and others are not being picked up for translation. Solution: We recommended the client to ensure they have a backup of their site, which can be done using the UpdraftPlus plugin. Next, we advised trying to translate the strings directly through WPML's String Translation interface. This can be accessed from the WPML menu in the WordPress admin area. The client should search for the strings under the 'gravityforms' text domain and add translations as needed. It was also noted that some strings, such as 'Choose file' and 'Max file size', are browser-dependent and therefore cannot be translated through WPML as they will appear in the language set by the user's browser.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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.
Problem: The client reported that WPML overwrites Gravity Form in the latest versions of Gravity Forms Multilingual, despite a previous workaround. They requested a new solution for this recurring issue. Solution: We revisited the previous workaround and found it still applicable. Here are the steps to implement the solution: 1. Open the file at /gravityforms-multilingual/inc/gravity-forms-multilingual.class.php. 2. On line 685, replace:
$snh = new GFML_String_Name_Helper();
with:
$snh = new GFML_String_Name_Helper();
// WPML workaround for compsupp-7768
$check = new \WPML\Utils\DebugBackTrace();
if ($check->is_class_function_in_call_stack('GFFormDisplay', 'process_form')) {
return $form;
}
3. Repeat the same replacement on line 822.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. 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. For further assistance, visit our support forum at https://wpml.org/forums/.
Problem: You have translated your site from Danish to English and added links in the main menu. However, when switching languages, two of the links, 'Going on' and 'about', revert to the Danish version despite re-translating the menu. Solution: To ensure that all menu links remain in English when switching languages, you should not attempt to translate templates or menus directly within the site editor. Instead, navigate to WPML > Translation Management > Dashboard. Use the filter on the top left to select the post type you wish to translate. After selecting your content, send it to translation. If you are translating the content yourself, you will need to access the translation at WPML > Translations. For further guidance, refer to our documentation on translating content created using the Gutenberg editor and full site editing at Translating sites that use full site editing.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are using WPML to translate your website and have configured products to be translatable, using the original language as a fallback. However, on the product category page, while products are visible even if not translated, the attributes/filters on the sidebar are not showing up in the German version because no products are assigned to them. Solution: If you have set products to use the default language as a fallback and translated the attributes, but none of the products is translated, nothing will show on the attributes archive pages. To resolve this, you can duplicate all the English products into German. For more details, please read our guide on displaying content in the default language for products and displaying untranslated content on pages in secondary languages. If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: After reinstalling WPML, the client encountered an error where a necessary folder for storing .mo files was not being created, and thus, the folder was not writable. This issue persisted even after the hosting company attempted to intervene by increasing site memory and manually adding the folder. Solution: We recommended manually creating the folder path for WPML's .mo files using an FTP program or through the admin control panel. This step ensures that the folder exists and can be checked for the correct writable permissions. Additionally, we suggested running a troubleshooting tool available at WPML's troubleshooting page to resync translations and verify if automatic translation functions correctly after these adjustments.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your current setup, 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 the problem persist, please do not hesitate to open a new support ticket with us for further assistance.
You are experiencing a translation issue on your WooCommerce frontend after updating to WordPress 6.7, despite implementing a fix from a Git repository.
Solution:
We recommend following these steps to address the issue:
1) Navigate to WPML>>Settings>>Custom XML Configuration. 2) Insert the following language configuration code in the Custom XML Configuration editor and save:
3) Visit the frontend. 4) Go to WPML>>String Translation and translate the strings, then visit the cart page.
Ensure to perform a full site backup before applying these changes. If necessary, adjust the language of the strings to English or add strings for the Cart page in German using the PowerPack Pro widget, as detailed in our guide on how to change the source language of strings.
If this solution does not resolve your issue or seems outdated, please check our related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client accidentally upgraded their subscription from Multilingual CMS to Multilingual Agency and wanted to downgrade back to Multilingual CMS and then renew it with a 25% discount. Solution: We resolved the issue from our side. We recommend checking the email sent from hello@wpml.org for further details on the downgrade and renewal process.
Please note that this solution might be outdated or not applicable to your specific case. If this solution does not resolve your issue, 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.
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 needed, please open a new support ticket for further assistance.
Problem: The client was unable to change the 'read more' and search placeholder texts in the Dutch language using the Kadence Builder, despite the strings being translated in WPML's String Translation section.
Solution: We discovered that the issue was related to how Kadence Builder's custom fields were registered with WPML. To resolve this, our team created a custom XML configuration to ensure these fields are recognized and translatable by WPML. Here are the steps we followed:
1. We examined the content inside the database of the main query post type to understand how the blocks were structured.
2. We created a custom XML configuration and added it to WPML > Settings > XML config tab. The XML code used was:
3. After saving the XML configuration, we made a small edit and saved the default language edit page, then updated the translated version with the correct placeholder text.
This solution allowed the 'read more' and search placeholder texts to display correctly in both languages on their respective pages.
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: The client created a variable product in WooCommerce and needs to translate the name of the default variation. After translating, the product appears empty in the frontend. Solution: 1. Ensure the WooCommerce Multilingual & Multi Currency plugin is installed and activated. You can download it from here. 2. Edit the variable product in the default language ensuring that the "WPML Translation Editor" is enabled. 3. Translate the secondary language product using the WPML Translation Editor. For detailed steps, refer to this documentation. 4. If the variation still does not show in the frontend, follow these troubleshooting steps: - Clear the cache in WPML. - Synchronize posts taxonomies. - Remove ghost entries from the translation tables. - More steps can be found in the WPML Support Troubleshooting page. 5. Consider creating global attributes and translate them either during the product translation or via WooCommerce >> WooCommerce Multilingual & Multicurrency > Attributes tab.
If these steps do not resolve the issue, 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.
Problem: The client was unable to open the Elementor editor for a translated page/template, resulting in a 403 Forbidden error and an uncaught TypeError. Solution: The client said he had found a folder named /he/ on the server. Removing this folder solved the problem. If this solution is 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 open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the currency switcher does not affect the currencies displayed in sidebar widgets on the homepage, despite working correctly on product and category pages. Solution: We recommend deleting the
object-cache
and
advanced-cache
files from the wp-content folder on your staging site. This approach resolved a similar issue on our local test site, suggesting that cached data might be preventing the currency switcher from updating the sidebar widgets 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. Additionally, please feel free to open a new support ticket with us for further assistance at WPML support forum.
Problem: In the Spanish version of a multilingual webshop, the client is unable to set display conditions in Elementor for the Spanish category 'JUEGO TABLAS'. Despite the taxonomy hierarchy being synchronized, only Slovenian categories are available for selection. Solution: We discovered that the issue was due to the use of an outdated 'Products' widget in Elementor, which was deprecated since version 4.1.3. We recommended switching to the 'Products Grid' widget. After making this change, the client should verify if the translated archive displays correctly by checking the front end.
If this solution does not resolve the issue or seems outdated, we highly recommend checking related 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
