Problem: The client is unable to add an existing user as a translator on their site; the interface just displays a blank page. Solution: 1. We recommend trying with a different user account, preferably a new one created with admin rights, to see if the issue persists when attempting to add translators. 2. Check for JavaScript errors by opening the browser's developer tools (press F12 or right-click and select 'Inspect'). 3. We found that updating the WPML plugin to version 4.7.3 resolved the issue, although it also worked in a sandbox environment with version 4.7.2. It's possible that disabling and re-enabling plugins or clearing cache might resolve the issue.
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 the problem persists, please open a new support ticket.
Problem: You are trying to set the thousand separator and decimal separator per language in WooCommerce Multilingual & Multicurrency, specifically for displaying prices in Euros with the correct formatting for different countries like Ireland, where the expected format is €1,914.00 instead of the European format €1.914,00. Solution: Currently, there isn't a direct way to adjust these settings through the UI for secondary currencies. However, we can achieve this by using WooCommerce filters. We have added the necessary code as a Code Snippet on your site. Here is the code you can use:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
/**
* Force formatting euro prices for the Ireland language
This code will specifically change the thousand and decimal separators for prices when the site’s language is set to Irish English ('en-ie').
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: The client was unable to see glossary entries and terms were being translated into a new language. There was confusion about automatic translation between two English variants and issues with glossary visibility after language deactivation. Solution: 1. We clarified that automatic translation does not work between two languages mapped as the same language, such as translating English into another variant of English. However, content can be duplicated in bulk from one English to another using the Translation Management tool. For more details, see the capture here: WPML Translation Management Dashboard. 2. The glossary was not visible because the English language was deactivated in WPML. Reactivating the English language resolved the issue. We are awaiting further feedback from second-tier support regarding the potential bug related to creating a glossary from a custom language. 3. A new version of the Advanced Translation Editor (ATE) has been released, which should resolve the issue. We recommend updating to this latest version.
If this solution does not apply to your case, or if it seems outdated, 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. If issues persist, we highly recommend opening a new support ticket at WPML support forum.
