Problem: The client reported an issue where variable products randomly displayed as 'out of stock and unavailable' after WPML was uninstalled. The client suspected that WPML might have been uninstalled incorrectly, potentially leaving duplicate variations in the database. Solution: We recommended following a specific guide to ensure that WPML was uninstalled correctly, which can be found here: WPML Reset Guide. If the problem persists after following the reset process, it is unlikely that WPML is the cause. We suggested further investigation by allowing us access to the site to potentially escalate the issue to our second-tier supporters. We also emphasized the importance of security and privacy, advising the client to back up site files and database before providing access, and preferably sharing access to a staging site if available.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing issues with the flag icon not appearing in the main menu after switching to 'auto translate everything' mode in WPML, despite not clicking the 'Sync Menu' button or manually creating translations. Additionally, you encountered a PHP Fatal error indicating an exhausted memory limit. Solution: First, increase the WordPress memory limit by adding the following lines to your wp-config.php file:
Add these lines above the '/* That's all, stop editing! Happy blogging. */' line. This adjustment should help resolve the memory issue and allow for smoother operation of WPML functionalities.
Next, ensure your site key is correctly registered to use automatic updates. If updates are not working, generate a new site key by deleting the current site URL from your WPML account at https://wpml.org/account/sites and re-adding it. This action will provide a new site key. Then, unregister and re-register WPML on your site with the new key by navigating to Plugins -> Add New -> Commercial tab and following the prompts to update or enter the new site key.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your specific case, 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client was unable to find and translate a specific string in the header of their website using WPML. Solution: 1. To make the custom Marquee Elementor element compatible with the WPML Translation Editor, we added the following XML configuration in WPML >> Settings > Custom XML Configuration section:
After this, we made a small change in the default language header template and translated the header in the secondary language. This made the marquee element content available for translation. 2. For translating the 'Donation' text, we followed these steps: - Navigated to WPML >> String Translation page. - Clicked on the 'Translate texts in the admin screen' link at the bottom of the page. - Searched for the string and enabled its translation. - Assigned the correct source language and added the translation of that string. - Cleared the cache to reflect the updated translation. For further details, you can refer to the following documentation links:
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: If you're experiencing an issue where a title on one of your pages in Elementor is not translated, despite being translated in the string search, we can help. Solution: We recommend you follow these steps: 1. Navigate to WPML >> Settings > Custom XML Configuration section. 2. Remove the following XML code:
3. Make a small change in the default language heading element and save the page. 4. Open the translated page, and the heading element should now be available for translation.
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: The client was facing an issue where despite translating everything in string translations, the cart was not translated. Additionally, a new cart page with the URL '/cart-2/' was automatically being created and set as the default, which was happening on multiple websites using WPML. Solution: We recommended checking if the 'Auto-generate from title' option was enabled in WPML>>Settings>>Translated documents options>>Page URL settings, as WPML follows WordPress guidelines for creating post slugs. If a post slug 'cart' exists, WordPress will automatically add 'cart-2' for a new post with the same slug. For more details, refer to the documentation on translating page and post URL slugs at https://wpml.org/documentation/getting-started-guide/translating-page-slugs/#translate-page-and-post-url-slugs and https://crocoblock.com/knowledge-base/articles/how-to-create-wordpress-slugs-and-permalinks/.
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 at WPML support forum.
Problem: You are trying to translate items via the WPML editor for your site, but the translated items are not displayed on an archive page. Solution: This issue might be due to the use of the FacetWP plugin on your archive page template. FacetWP is compatible with WPML, but it requires the installation of a bridge plugin to function correctly with WPML. You should have received a notification about this in your WordPress admin. We recommend that you install the bridge plugin and follow the guides provided by WPML and FacetWP for setting up multilingual filters:
After installing the bridge plugin, please verify if the translated items appear as expected on the archive page.
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: The client was unable to use the automatic translation feature in WPML due to incorrect account type and subsequent errors after reinstallation, including authentication errors and missing translation options. Solution: 1. We recommended increasing the WordPress memory limit to at least 128MB, ideally 256MB, by adding the following code to the wp-config.php file:
2. We advised generating a new key for the domain via WPML account sites, unregistering the old key, and re-registering WPML with the new key. 3. After addressing these issues, the automatic translation feature began to function correctly.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, please 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, you can also visit our support forum at WPML support forum.
Problem: The client was experiencing issues with ACF Pro select fields not displaying correctly or being translated on their development site, despite following the WPML documentation. Solution: 1. We first verified the usage of ACF fields on the specified page but did not find any. We requested the client to highlight the fields using a screenshot. 2. Upon further inspection, we identified that the wrong ACF field was used in the page builder. We corrected the 'designer' ACF field, and it displayed correctly afterward. We asked the client to double-check the changes.
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 at https://wpml.org/forums/forum/english-support/.
Problem: The client is unsure about the importance and functionality of the 'translate link targets' option in WPML. Solution: If you're experiencing confusion regarding the 'translate link targets' in WPML, it's important to understand that this feature is designed to help manage internal links in your multilingual site. When you insert internal links in a page or post, WPML automatically recognizes these as internal links and, if a translation is available, WPML will adjust the link to point to the translated version of the linked page. This feature is generally a troubleshooting tool and does not need to be used regularly unless you notice that some internal links are not being translated correctly.
Please note that this solution might be irrelevant if it's 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 at WPML support forum for further assistance.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
