Problem: The client has translations in .po/.mo files within the languages directory of their child theme and wants WPML to use these translations instead of its own.
Solution: We recommended ensuring that the translation file names match the language locale. The client can verify the language locale by navigating to WPML >> Languages >> Edit Languages. We provided a link to the WordPress developer documentation for further guidance on using
If the solution provided here does not apply or is outdated, we suggest opening a new support ticket. We also 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. For further assistance, please contact us through the WPML support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client needed a way to display a specific language on a WPML-managed multilingual site based on conditions such as browser language and geolocation. Additionally, they wanted to set a non-default language to be shown first when visiting the site. Solution: We informed the client that WPML allows displaying a language based on the user's browser language. We provided a step-by-step guide on setting up automatic redirection based on browser language, which can be found here: https://wpml.org/documentation/getting-started-guide/language-setup/automatic-redirect-based-on-browser-language/. Furthermore, we mentioned the possibility of setting a root page where users can select their preferred language before browsing the site. Details on setting up a directory for the default language can be found here: https://wpml.org/documentation/getting-started-guide/language-setup/directory-default-language/.
Please note that the solution provided might be irrelevant if it's 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 you still need assistance, please don't hesitate to open a new support ticket with us.
Problem: The client needed to disable automatic translation for a specific page because it was preventing visibility of custom translatable fields in the Advanced Editor. Solution: We recommended setting the field
mfn-page-items
to Translate and then re-translating the page. We provided a step-by-step guide through our documentation:
If the provided solution is irrelevant due to 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 issue persists, please open a new support ticket with us.
Problem: The client is developing a site with WPML and needs to set Italian as the default language after initially creating content in English. They are concerned about potential issues with changing the default language in WPML and how to configure the site so that visitors who enter
https://mysite.com
are redirected to the Italian version of the site. Solution: We recommend setting Italian as the default language from the start and translating the theme from there. Theme strings will still be identified as English, but this will not affect the content. If the client has not yet created content, this is the best approach to avoid issues later on. .
If this solution is not relevant due to being outdated or not applicable to the client's case, or if further assistance is needed, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the issue persists, the client should open a new support ticket: Contact WPML support.
