Problem: The client is using DeepL for automatic translations on their website with German as the default language, and includes Turkish and English. They need the English translations to consistently use American English (EN-US) due to differences in spelling and vocabulary. They are concerned that DeepL's output might default to British English (EN-GB) or be inconsistent, and they are unsure how to configure WPML's DeepL automatic translation engine to always translate to American English (EN-US). Solution: We recommend checking the translation Formality setting of the DeepL translation engine to see if adjusting it improves the results. Here is how you can adjust the Formality: https://wpml.org/documentation/automatic-translation/translate-your-wordpress-site-with-deepl/#deepl-formality Please note that WPML uses DeepL's API for automatic translations, and most of the translation processing occurs on DeepL's side, so we have limited control over the output. Additionally, WPML does not yet include a feature to provide hints to the translation engine regarding how the translation should appear. You can also experiment with custom language settings in DeepL to see if you get a translation that meets your needs. For more information on using custom languages, refer to the guide here: https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/ If you want specific words to appear in a particular way, it's best to use the Glossary feature and configure how those words should be translated.
If this solution does not resolve your issue or 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue with an overly wide menu dropdown on both desktop and mobile versions of their website. Solution: We discovered that custom code was causing the menu dropdown to be too wide. We adjusted this for the client. If you're experiencing this, we recommend you try adjusting the width by navigating to Divi > Theme Options > Custom CSS, and modifying the width on line 24.
Please remember that the creation and maintenance of custom code is beyond our usual support scope. 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You have a website in three languages using WPML, and you're encountering unwanted text at the end of the Turkish language menu. Solution: First, we recommend navigating to the Turkish menu to correct it directly. For guidance on translating WordPress menus with WPML, please visit Translating WordPress Menus with WPML. If the unwanted text persists as an incorrect translation, consider using the glossary feature to manage specific translations. Learn how to create and manage glossary entries here: How to Create and Manage Glossary Entries.
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 for further assistance.
Problem: The client ordered 200,000 translation credits for use on a specific website but was unable to find all the credits in the backend. Only a small number of translations appeared to have been processed, and there was difficulty in transferring or properly allocating the remaining credits to the correct destination. Solution: We discovered that the site had been moved, resulting in the creation of a new organization. We resolved the issue by merging the old organization with the new one, which should now reflect the correct allocation of translation credits.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client needs to convert country names to country abbreviations (e.g., DE, EN) in a WPML language switcher without using flags. Solution: If you're experiencing this, we recommend you try the following steps: 1. Navigate to WPML >> Languages page. 2. Click on the Edit Languages link. 3. Enter the country codes (DE, EN, etc.) in the Translation text boxes. 4. Click the Save button. 5. Click on the Pencil icon to open the “Language Switcher Settings”, uncheck the “Flag” option, enable the “Native language name” option, and then click the Save button. 6. Clear all sorts of site/server/CDN cache.
This solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum.
Problem: You have configured WPML and set a size for the flags of other countries. The base language flag appears fine, but the flags of the other languages are too big, affecting both desktop and mobile versions. Solution: We recommend you go to your site's backend > Appearance > Customizer > Custom CSS and add the following CSS code:
img.wpml-ls-flag {<br /> width: 18px !important;<br />}
This should make the flags of the other languages the same size as the base language flag.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: If you're unable to assign purchased DeepL credits for translation in WPML, it might be due to the automatic translation account ID being reset. This can happen if you uninstall/reset WPML or reinstall/set WordPress from scratch, causing a new ID to be generated and the credits to remain in the old account. Solution: We have located the credits on the older account and moved them to your current account. You should now be able to see them by navigating to WPML > Translation Management > Tools in the top-left area of your site. Please confirm that you can see the credits in the backend of your site.
If this solution does not resolve your issue or seems irrelevant due to it 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.
