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.
Problem: The client is unable to translate content created with BeBuilder on their BeTheme-based website using WPML. Despite setting BeBuilder data storage to Serialized | Readable format and updating all pages, WPML does not recognize the BeBuilder elements for translation.
Solution: We recommend performing a full site backup before proceeding with any changes. After securing your backup, please follow the workaround provided in the WPML errata page for issues with BeTheme and BeBuilder content not being available in the translation editor. You can find the detailed instructions here: https://wpml.org/errata/betheme-bebuilder-content-not-available-in-translation-editor/
May you need to make the mfn-page-objects field also as translatable.
Please note that this solution might be outdated or not applicable to your case. If after checking the errata and ensuring you have the latest versions of themes and plugins the issue persists, we encourage you to open a new support ticket. We also highly recommend visiting the WPML known issues page to verify if there's a permanent fix for your version. If further assistance is needed, please contact us in the WPML support forum.
Problem: The client added a drop-down language switcher to the main menu and styled it to match the menu items, but encountered an issue where the switcher did not have a transparent background. Additionally, there was an unstyled switcher appearing on the right side of the menu on the home page. Solution: We suggested that the unstyled switcher might be generated by a different plugin or the current theme. To resolve this, we recommended disabling the switcher from the backend of the site if the plugin or theme provides such an option. Alternatively, the switcher can be hidden using CSS code. We offered to provide a CSS code example to hide the switcher if we had access to the site.
Please note that this solution 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 you still need assistance, please open a new support ticket.
Problem: The client installed WPML and expected that switching the language using the WPML switch in the admin bar would change the WordPress panels and sidebar language accordingly. However, this was not happening. Solution: We explained that WPML is designed to keep the backend language consistent, regardless of the language selected in the backend top bar. This is a preference expressed by many of our users. To set the WordPress administration language, we provided a link to our documentation: Setting the WordPress Administration Language.
If this solution does not apply to your situation, or if it seems outdated, we encourage you to check for related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. Should you still encounter issues, please do not hesitate to open a new support ticket with us. For further assistance, you can reach out to our support forum here: WPML support forum.
