Problem: The client was facing an issue where different shipping costs set for shipping classes in each currency were not reflecting correctly on the cart/checkout page. Instead of the expected 3999kr, the shipping cost displayed was 299kr. Solution: We advised the client to ensure that the shipping classes were translated correctly by following the steps in our documentation: https://wpml.org/documentation/related-projects/woocommerce-multilingual/#shipping-classes. We also recommended updating all outdated plugins and resetting WPML's language tables. This involved creating a full site backup, updating plugins, and performing specific WPML troubleshooting steps to reset and repopulate language settings. For products existing only in one language, we guided the client to adjust settings under WPML -> Settings -> Post type translation to ensure only translated products are shown in secondary languages.
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 do not hesitate to open a new support ticket at WPML support forum.
Problème : Vous rencontrez un problème de connexion WPML avec votre site et recevez le message d'erreur : 'WPML could not load configuration files, which your site needs.' Vous vous demandez comment résoudre ce problème et pourquoi WPML ne peut pas charger les fichiers de configuration. Solution : 1. Consultez le journal des erreurs détaillées pour identifier le type d'erreur. Recherchez des messages tels que :
Problem: The client is experiencing issues with automatic string translation in WPML, where the translation process is stuck, showing only the cog symbol. Despite attempts to delete the automatic translation jobs in troubleshooting, they are not being successfully removed. Solution: We recommend trying the beta versions of WPML, which include changes to the string translation process. These beta versions can be tested on a staging site or a separate copy of the site to avoid affecting current work. You can download the beta packages from https://wpml.org/account/downloads/.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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 at WPML support forum for further assistance.
Problem: If you're experiencing issues with the WPML language switcher not appearing in your menu after enabling it in the settings, and the settings disappear after saving, the problem might be related to insufficient WordPress memory limit or specific menu settings. Solution: 1. Increase the WordPress memory limit to at least 256M. You can do this by adding the following code to your wp-config.php file:
Add this code above the line /* That's all, stop editing! Happy blogging. */. 2. Ensure your menu is fully translated as per the WPML guide on translating menus, which can be found here: Translating Menus Guide. 3. Add the language switcher in WPML -> Languages and verify if the issue is resolved. 4. If the language switcher still does not appear, it might be hidden due to CSS classes such as "desktop-link-hide". Consult with your website's developer or the person who manages your site's styles to adjust this.
If these steps do not resolve your issue or if the solution seems outdated or not applicable 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 needed, please open a new support ticket at WPML Support Forum for further assistance.
