Problem: If you're experiencing issues where the content of a category disappears when switching languages in your store, it might be related to a theme conflict. Solution: We recommend trying the following steps to isolate the issue: 1. Switch to a default WordPress theme. 2. Keep only WPML/WCML Plugins and essential plugins active. 3. Disable all other plugins. Please ensure you have a full backup of your files and database before making these changes. If reverting to a standard theme resolves the problem, it indicates a theme issue. In such cases, contacting the theme developers is advisable.
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 open a new support ticket at WPML support forum.
Problem: The client is seeing a notification about new translatable content but is unsure if they need to update the MO files regularly since they do not receive notifications to do so. Solution: We explained that the notification indicates the availability of new translatable content. It is not mandatory to update these MO files, especially if the strings are already translated as desired. We recommended that in the future, if the client cannot find a specific string, they should consider scanning the plugins and/or theme to find it. However, this is not necessary at the current moment.
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 issues with global element updates not being imported correctly, such as background colors, and has questions about the 'post types translation' settings for global styles in the Avada theme. They are also concerned about notifications for updates to strings. Solution: We recommend ensuring that the settings are consistent across all languages. If the settings are set differently for each language, WPML will maintain these differences. To synchronize the settings, you can import your settings from one language to another, such as from EN to FR. This process will overwrite all old options with the imported settings. For detailed steps on how to import theme options from one language to another, please visit https://wpml.org/documentation/theme-compatibility/using-wpml-with-the-avada-theme/how-to-set-theme-options-for-languages-in-avada/#how-to-import-theme-options-from-one-language-to-another. Moving forward, we suggest changing the settings for 'All Languages' to avoid similar issues.
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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing incorrect product quantities displayed next to the WooCommerce product filter in languages other than the default language on their website. Solution: To address this issue, follow these steps: - Navigate to Products -> Attributes. - Click "Configure terms" to access the "Kompatybilność" attribute terms. - Click on the number of products next to the problematic term to view all products in this term. - Select all products. - From the "Bulk Actions" dropdown menu, choose edit. - Change the status to "Publish" and update them.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: You are experiencing broken links in post content after switching your domain from learn.eformity.nl to learn.eformity.com and changing the default language from Dutch to English. English posts are showing Dutch links, and Dutch posts are showing p=xyz links. Solution:
We recommend re-saving your posts in bulk to see if this resolves the issue. This approach might correct the links to reflect the new domain and language settings. Before making any changes, it's advisable to perform these steps on a staging site if available, especially if you have a backup of your website. Additionally, before changing the default language, run the Translate Link Targets function to ensure all links are correctly set to the new domain.
This should ideally be done before you switch the default language.
If these steps do not resolve the issue or if the problem persists, 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 solution provided here is outdated or not applicable to your case, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problème : Le problème était lié à la classe de statut des propriétés qui ne s'affichait pas correctement en anglais Solution : Concernant les propriétés qui ne s'affichent pas en version anglaise, il semble que cela soit dû au paramétrage des widget du thème, et d'une mauvaise synchronisation des taxonomies.
Si ces solutions ne résolvent pas vos problèmes ou si elles semblent obsolètes, nous vous recommandons vivement de consulter les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support ici.
Problem: The client is experiencing 404 errors on their multilingual WordPress site managed with WPML. These errors are reported in Google Search Console and include pages in different languages that seem to be improperly generated or missing. The client also noted issues with URLs due to case sensitivity. Solution: We reviewed the sitemaps and confirmed that the problematic URLs provided by the client do not appear in the sitemaps, indicating that the issue might not be related to WPML. We suggest asking Google to recrawl the site to address the 404 errors showing in the Google Search Console. Additionally, we recommend following Google's methods for fixing 404 errors, which can be found here: Fixing 404 Errors on Google.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your specific 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 problems persist, please open a new support ticket with us for further assistance.
Problem: If you're experiencing issues with changing the RankMath title and description on a translated product in a specific language, while being able to make these edits in other languages, the issue might be related to WPML settings. Solution: We recommend you to navigate to WPML -> String Translation and look for any slugs strings (like "shop" from the domain "WordPress") that might be translated incorrectly. Correcting these translations can potentially fix the issue. After making these changes, please test if you are now able to edit the SEO title and description.
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 issue persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: If you're using the Final Tiles Gallery plugin on a multilingual WordPress site managed by WPML and encounter an issue where images on the English translation of a page keep loading indefinitely without displaying, the problem might be due to incorrect image links. Solution: We recommend you try the following steps: 1. Open the
3. Check the translated page on the front end to see if the issue is resolved.
Additionally, we suggest contacting the plugin authors to encourage them to join our Go Global Program.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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, you can also visit our support forum at WPML Support Forum.
Problem: The client is experiencing 404 errors on their website due to URLs that appear to be incorrectly encoded or truncated. This issue is particularly occurring with URLs containing non-Latin characters, such as Cyrillic for the Russian language. Solution: 1. We recommend enabling URL Encoding for languages with non-Latin characters to ensure that URLs are processed correctly. To do this: - Navigate to "WPML > Languages" in your WordPress admin dashboard. - Click on "Edit Language". - Find the "Encode URLs" option and select "Yes" for the Russian language. - Save the changes. 2. If a specific URL is still showing a 404 error, check if there is an extra character like
%B
at the end of the URL. Removing this character should resolve the issue. 3. For URLs that are still problematic, use a URL decoder tool like https://www.urldecoder.org/ to check for any incorrect characters. Remove any incorrect characters found.
If these steps do not resolve the 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 problems persist, please open a new support ticket.
Problem: You are operating a WooCommerce shop in two languages, German and English, and using Yoast SEO to create sitemaps. While the product URLs sitemap includes both languages, the product categories sitemap is only generated for German categories, not for English. Solution: We recommend installing and enabling the WPML SEO extension, which appears to be currently disabled in your setup. You can download and install it from https://wpml.org/documentation/related-projects/wpml-seo/. After installing, please recreate the sitemap and check if the product categories in the secondary language are now included.
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 WPML support forum for further assistance.
Problem: You are unable to translate custom post types created with ACF on your site. Solution: First, ensure that you have enabled the translation for custom post types in WPML. You can do this by navigating to WPML >> Settings > Post Types Translation section. For more detailed instructions, please refer to our documentation: Translating Custom Posts. If after following these steps, you still face issues with translating your custom post types, we recommend providing more details about the specific problems you are encountering.
Please note that the solution provided 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 do not hesitate to open a new support ticket. For further assistance, you can visit our support forum at WPML Support Forum.
Problem: The client reported that the Donate button was only functioning on the English version of their website, not on the Croatian version. Solution: We identified that the issue was due to multiple instances of the same ID being used for the Donate button, which is generated by the Donations Plugin. Here are the steps we took to resolve the issue: 1. Accessed the Elementor Header template in the default language. 2. Replaced the shortcode
[dp_donation_modal]
with
[dp_donation_modal_off]
in the template. 3. Advised the client to remove or replace the shortcode in other places where it appeared but was hidden in the desktop view. To avoid similar issues in the future, we recommended either using the button ID only once per page or updating the plugin code to use a class selector instead of an ID for JavaScript triggers. The popup should now work in both languages. We asked the client to confirm if the issue was resolved.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate to open 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, you can contact us directly through our support forum.
Problem: The client was experiencing an issue with a persistent pop-up appearing on their site after updating WPML. Solution: We addressed the issue by hiding two old instances of the site from WPML's records to prevent interference. In the WPML -> Troubleshooting section, we performed the following actions:
Synchronize local job ids with ATE jobs
Synchronize translators and translation managers with ATE
After these steps, we selected 'Copy' in the pop-up message, understanding it was a duplicate from an older instance. This resolved the issue, and the pop-up no longer appears.
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 the problem persists, please open a new support ticket.
Problem: You are importing and translating products from Polish (PL) to Latvian (LV), and your site's default language is Latvian. In WP All Import, you have marked that the import language is Polish. However, you expected to see products in Polish, but they are appearing in Latvian instead. Solution: The issue occurs because the Polish language is hidden, and a cron job is running. This is a known issue that we are currently tracking. As a workaround, we recommend you unhide the Polish language. You can find more details on a similar issue in our forum: https://wpml.org/forums/topic/problem-when-periodically-updating-items-via-cron/page/2/. Please try this workaround and let us know if it resolves the issue. We will keep you updated once a permanent fix is available in a future version of WPML.
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 issue persists, please open a new support ticket at our support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
