Problem: The client was unable to translate content into Norwegian using the DeepL translation engine; the system indicated it would start translating, but nothing happened. Solution: 1. As a temporary workaround, we recommended switching to the Google translation engine, which successfully translated the page into Norwegian. For guidance on changing translation engines, please refer to our documentation: How to Change Automatic Translation Engines. 2. Our 2nd tier support team identified the issue as being related to language mapping and the automatic translation engine. Our development team prepared a fix for this issue. 3. We asked the client to recheck the issue to confirm that the fix resolved the problem.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket with us for further assistance.
Problem: The client was unable to add Norwegian under language mapping for translation with DeepL, despite documentation suggesting it should be possible.
After further communication and the client's patience, we escalated the issue and were informed by our ATE department that Norwegian has been enabled with DeepL. We asked the client to check if the issue was resolved.
For account-related requests, such as resetting the year to start from a different date, we directed the client to contact our Accounts department via email at hello[at]wpml.org, as we handle only technical issues on the Support Forum.
If this solution doesn't look relevant to your issue, please open a new support ticket at the WPML support forum.
