Problem: The client needed to manually edit a translated article that was broken.
Solution: We recommended that the client deactivate the WPML Translation Editor before manually editing the content to avoid issues with synchronization that could result in overwritten content. We provided a link to our documentation on how to use different translation editors for different pages: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, we encourage you to check the 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 you still need assistance, please do not hesitate to open a new support ticket with us.
Problem: The client wanted to separate English into en_us and en_gb variations, with en_us as the default language and its URL changed from domain.com to domain.com/en_us/. They also wanted to implement en_gb at domain.com/en_gb/ while keeping all other languages unchanged. Solution: We advised the client that it is not possible to change the language code directly. Instead, we recommended creating custom languages with the en-us and en-gb codes. We instructed the client to: 1. Create a full backup of the database and website. 2. Follow the guide to create the en-us language and duplicate the content to the new language: https://wpml.org/faq/how-can-i-assign-or-change-language-code-to-existing-content/ 3. Add the language with the en-gb code by following this guide: https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/#adding-your-own-languages-using-wpmls-gui 4.Kindly note that you'll also need to use a different locale for the en_us language because this locale is already used for the default English language. Please check this errata page Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If so, 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 you still need assistance, please open a new support ticket: https://wpml.org/forums/forum/english-support/
Problem: The client wanted to display the language text next to the flag in the main menu only after clicking the flag to show the submenu. Solution: We suggested the following steps: 1. Navigate to WPML -> Languages -> Menu language switcher. 2. Adjust the language switcher settings to show the names of the languages by clicking on the pencil icon. 3. Add the following CSS code to the style.css file in the root folder of the website's theme:
If that does not work, we recommended trying to target the current language menu and the sub-menu items separately with this CSS:
.gp-nav .menu li a .wpml-ls-display{ display: none; } .gp-nav .menu li .sub-menu li a .wpml-ls-display{ display: inline-block; }
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 you still need assistance, please open a new support ticket.
Problem: The client moved their site to new hosting and encountered a notification issue after changing from a temporary domain back to the original domain. They were concerned about losing translation credits and the disappearance of product translations.
Solution: 1) We recommended increasing the memory limit for WPML by adding the following code to the
2) We identified that the issue might be due to the home URL being forced somewhere in the installation. We provided a guide to help resolve this: Using WPML on Two Domains.
3) After increasing the memory limit and addressing the home URL issue, we advised the client to open a page that previously had a translation to check if the translation still exists. If it does, they should send the pages for translation again, and they will appear as translated.
4) We suggested resending the translation jobs by following the guide: Sending Content for Automatic Translation. We recommended starting with one page and avoiding the option to translate it again if a message indicates that the page was already translated. Instead, choose to translate it manually, complete the translation, and then apply the same process to other pages.
If the solution provided here is not relevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at WPML 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 in our support forum.
Problem: The client is unable to find strings to translate for WooCommerce Subscription emails in a multilingual website. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML > Theme and Plugins Localization. 2. Select the WooCommerce Subscriptions plugin and scan it for strings. 3. Proceed to WPML > String Translation. 4. Under the 'domain' filter, select "woocommerce-subscriptions". 5. Translate the strings that you wish to localize.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If you still need assistance, do not hesitate to open a new support ticket. We highly recommend visiting the WPML support forum for further guidance.
Problem: The client made changes to various PHP files in their theme, but after rescanning the files in WPML, the changes did not appear in the string translations. Additionally, text domains were not being scanned correctly, and even after correcting an incorrect text domain, the old one still appeared in the list of text domains for their theme. Solution: We recommended the client to follow a guide on translating PHP strings, which can be found here: https://wpml.org/documentation/support/translating-the-theme-you-created/. Furthermore, we advised the client to check a specific reply that outlines steps to resolve issues with string translation not working for some admin strings, which can be accessed here: https://wpml.org/forums/topic/string-translation-not-working-for-some-admin-strings-checkout/#post-10964017.
If the solution provided is not relevant 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. Should you need further assistance, please do not hesitate to open a new support ticket. You can reach the WPML support forum here: https://wpml.org/forums/forum/english-support/.
Problem: The client was trying to translate menus from English to Arabic and encountered an issue where the mobile Arabic menu was not being displayed.
Solution: We noticed that the CSS property
display: none
was applied to the class
difl_advancedmenuitem_1_tb_header
, which caused the menu to be invisible on mobile devices. To fix this, we suggested adjusting the CSS or the settings that control the display property of this class. Here is an example of the CSS code that could resolve the issue:
@media only screen and (max-width: 980px){<br />.difl_advancedmenuitem_1_tb_header {<br /> display: block !important;<br />}<br />}
If this solution does not apply to your case, or if it seems outdated, we 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 was trying to translate a page with ACF Custom fields and encountered an error:
WP_Text_Diff_Renderer_Table::__isset()
. The issue was visible in the admin page for translating a selected post, where instead of the expected content, a RuntimeException occurred stating 'Could not retrieve field contents for job_id: 3', along with a deprecation notice for a property
_base64
not being declared.
Solution: We recommended the client to update the WPML plugins to the latest version by navigating to Plugins -> Add New -> Commercial tab and then check if the issue still persists.
Please note that the solution provided might be outdated or not applicable to your case. If after following the steps the issue remains, we encourage you to open a new support ticket. We also 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 need further assistance, please visit our support forum.
Problem: The client reported an issue on a WordPress multisite where administrators could log out without any problems, but other roles encountered an 'Internal Server Error' when attempting to log out. The issue did not occur when WPML was deactivated. The client identified that the problem occurred when the 'Set admin language as editing language' checkbox was not marked or when the language was not set to the site's default.
Solution: We recommended the client to: 1. Ensure a full backup of the website and database. 2. Deactivate all plugins except for WPML and its addons to check if the issue persists. 3. Reactivate each plugin one by one, checking for the issue after each activation to identify any conflicts. 4. If the problem remains, repeat the steps with the parent theme and a default WordPress theme (such as Twenty Twenty-One or Twenty Twenty-Four).
If the solution provided here is not relevant due to being outdated or not applicable to your case, we suggest opening a new support ticket. We also highly recommend checking related 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 contact us through the WPML support forum.
Problem: The client needed assistance with translating a WooCommerce store from Bulgarian to German. The products were still in Bulgarian, and the store's homepage was partly missing. Additionally, when clicking on a product, the client was redirected to the .com version in Bulgarian.
Solution: We recommended manually editing the translated page (German) using Zion Builder. Here are the steps we provided: 1. Edit the page in the original language. 2. In the right column, find the 'Languages' block. 3. Select 'WordPress Editor'. 4. Select the scope of the change. 5. Save the changes.
We performed these steps on the staging site, and the client could see the results.
If this solution does not apply to your case, or if it seems outdated, we encourage you to check the related known issues, verify the version of the permanent fix, and confirm 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 was experiencing an issue where the layout of the translated page, which was built with custom fields, was broken and not all CSS styles were working.
Solution: We checked the site and found that the field groups did not have a translation mode set. We selected "Same fields across languages" in the About Us field group. Then, we updated the page in the default language and its translation. We advised the client to edit their field groups to select the translation mode and provided a guide for reference: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we recommend 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. If further assistance is needed, please contact us in the WPML support forum.
Problem:
Some of the parts on home page were not being translated, while using Elementor as page builder.
Solution:
We recommend checking the guide on Registering Custom Elementor Widgets for Translation. It's possible that some Elementor widgets may need to be recognized by WPML. By following the guide, you can ensure that these widgets are translated and displayed correctly on the frontend.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. 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 the issue persists, please open a new support ticket so we can assist you further.
Problem: The client is seeking information on how to use the REST API with WPML to retrieve pages in different languages and understand the relationship between translations.
Solution: We recommend checking the following guides for more information:
Please note that the solution provided might be outdated or not applicable to your case. If so, 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:
If you're experiencing issues with translating content created with Elementor using WPML, where only the page title appears but not the content, and the header appears buggy on the translated page, follow these steps for a solution. Solution:
1) Install and activate the Multilingual Tools plugin.
2) Generate the WPML Language configuration file for the Custom Elementor Widget as explained in our documentation on Registering Custom Elementor Widgets for Translation.
3) Navigate to WPML >> Settings >> Custom XML Configuration tab.
4) Add the language configuration in the Custom XML Configuration field.
5) Save the changes.
6) Open the Homepage for editing in the default language.
7) Update it to refresh the translation settings (just resave).
After completing these steps, please proceed with the translation of the Homepage and check if you are getting the expected results. Remember to update other pages in the default language as well to refresh their translation settings.
If this solution does not apply to your case, or if it seems outdated, 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. Should you still encounter problems, please do not hesitate to open a new support ticket in our support forum.
Problem: The client was experiencing issues with WPML automatic translation credits after migrating their site. Initially, they tested WPML on local servers, then moved to a test domain (A), and finally to the actual domain (B). They encountered a warning about an unregistered license of WPML and were unable to assign auto translation credits, as the domains were not listed in their account. Additionally, they were unable to move credits back to their WPML account and the 'Tool' tab was missing under the 'Translation Management' tab.
We then asked the client to try removing the sites using the blue button in their WPML account here: https://wpml.org/account. After the client provided more information, we were able to locate and move 86,310 stuck credits back to their account.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, 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 for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
