Problem: The client needed to display the currency differently based on the language on their site. Specifically, they wanted to change the position of the currency symbol between French and English versions. They were struggling with the currency position not being adjustable via the usual WPML settings. Solution: We recommended using the WPML > String Translation to adjust the currency symbol position and separators. First, the client should edit the options in WooCommerce to make these strings available for translation:
admin_texts_woocommerce_price_decimal_sep
woocommerce_price_decimal_sep
admin_texts_woocommerce_price_thousand_sep
woocommerce_price_thousand_sep
admin_texts_woocommerce_currency_pos
For adjusting the position of the currency symbol, the client should go to WPML > String Translation and use the 'Admin Texts Translation' to search for 'Position'. After finding the correct string, they should add it to the WPML String Translation to translate its values into different languages. For example, translating from 'left_space' to 'right_space' in German should display the EUR currency symbol to the right without a space character. If these steps do not resolve the issue, it may require custom code as it could be a limitation of WooCommerce rather than WPML. For more detailed guidance on changing the currency symbol, please refer to https://woocommerce.com/document/change-a-currency-symbol/.
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: After migrating from qtranslate to WPML, the client noticed that while the English translations are visible on the frontend, they do not appear in the WPML editor for pages; however, articles are displayed correctly. Solution: The issue arises because the translations were manually created without using WPML's translation workflow, leading to no data being associated with these translations in the Classic Translation Editor. We recommend two potential solutions: 1. Switch to the Advanced Translation Editor (ATE), which supports automatic translation. This change might require retranslation and could incur translation credit costs. For more details on how to switch, visit Switching from Classic to Advanced Translation Editor. 2. Continue using the Classic Translation Editor if you prefer full control over the translations, though this method is less convenient and more manual.
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 was trying to fix the database after importing data from qTranslate using the appropriate plugin in a sandbox environment, aiming to replicate the actions on the live site. However, they encountered an issue where the website displayed an almost blank page instead of the expected content. Solution: We recommended the following steps to address the issue: 1. Ensure all qTranslate settings are saved. 2. Deactivate qTranslate X from the Plugins admin page. 3. Ensure WPML is activated but not yet configured. 4. Install and activate the QT Importer. 5. Navigate to Options -> QT Importer and click Start. Additionally, we asked the client to create a full backup of the site experiencing issues and share site credentials for further investigation. Upon review, it was discovered that a fatal error related to the theme was causing the issue.
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.
Problem: You are experiencing an automatic language switch in your admin profile and incorrect amounts on invoices when saving orders due to a language mismatch. Solution: First, ensure that you update WooCommerce to the latest version. If the problem persists, disable all non-WPML plugins except for WooCommerce and switch to a default theme. Remember to clear all caches. After these steps, check if the issue still occurs. If it does, we will escalate this to our second-tier support.
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 at WPML support forum.
Problem: You are looking for a plugin recommendation for setting up a multistore with different domains, both multilingual, that works well with WPML. Solution: We recommend using the WooCommerce Multistore plugin for WooCommerce platforms. This plugin allows you to manage multiple stores across different domains or subdomains and integrates well with WPML for handling translations and multilingual content. Ensure that each store in the multistore setup is configured correctly for WPML compatibility and test the setup thoroughly during development to ensure smooth operation across domains.
If this solution becomes irrelevant, outdated, or 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 at WPML support forum.
Problem: You are experiencing a critical error when accessing backend pages in French after upgrading to PHP 8.4. The error results in headers appearing but the content remains empty, and a critical error message is displayed. Solution: First, we recommend enabling the WordPress debug log to capture more specific error details. You can do this by editing the
After setting these, try to reproduce the issue and check the debug log in
/wp-content/debug.log
for any specific error messages. Share these details via a secure method like pastebin.com for further analysis.
If the issue persists, consider downgrading your PHP version to 8.2 as PHP 8.4 may not be fully compatible with WPML or even WordPress itself. This step should help resolve the compatibility issues you are facing.
If these steps do not resolve your issue or if the solution becomes irrelevant due to updates or specific circumstances, 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 personalized assistance at WPML support forum.
