Problem: The client was updating string languages and encountered an issue where the theme header was not functioning correctly after changing the language. The header appeared broken and did not display as expected. Solution: We recommended the client to check if they were planning to use the first two headers that appeared on their site's header builder page. If those headers were not needed, we advised the client to delete them and then check if the issue with the theme header was resolved.
Please note that this solution might be irrelevant due to it being outdated or not applicable to your case. If the problem 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 do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client is using the Borlabs cookie plugin and has noticed that the
wp-wpml_current_language
cookie is set as an essential cookie. The issue is that this cookie is set immediately when the page loads, before any consent is given through Borlabs. Solution: We explained that the
wp-wpml_current_language
cookie is indeed set when the Ajax cookie option is active, as it is necessary for WPML to function correctly, particularly for filtering Ajax calls during the initial page load. This behavior is documented in our support article, which you can read here: WPML Browser Cookies.
If you're experiencing this issue, we recommend you to understand that the
wp-wpml_current_language
cookie is essential for WPML's functionality and cannot be delayed until consent is given. However, if this solution does not apply to your case, or if it seems outdated, please open a new support ticket. 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 need further assistance, please contact us in the WPML support forum.
Problem: The ATE doesn't load. Solution: We recommend clearing your browser cache as outlined in our errata on the Advanced Translation Editor (ATE) freezing issue. You can find the instructions here: https://wpml.org/errata/advanced-translation-editor-ate-freezing-issue-on-certain-browsers/. If this does not resolve the issue, we suggest trying a different browser to see if that fixes the problem.
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 open a new support ticket in the WPML support forum.
Problem:
Translation Editor doesn't open for some pages Solution:
Doing a slight edit to the content forced WPML to reload the page's elements again, and the translation editor ATE is working then.
1- Edit the concerned page
2- add a slight change like a space or a dot
3- WPML icon will change to a double arrow (Which mean it detected new elements)
4- Click on that icon to open ATE
Problem: The client is trying to edit a few menu items that are auto-translated and synced but is facing issues due to the automatic sync feature. Solution: We recommend the following steps to edit the translated menus: 1. Go to Appearance -> Menus. 2. Switch the language from the top admin bar. 3. Select the translated menu. 4. Edit it and save.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we encourage you to open 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 you need further assistance, please contact us in the WPML support forum.
Problem: The client is experiencing an issue with the Advanced Translation Editor where they cannot add or update translations, which seems to be related to tinyMCE.
Solution: We recommend clearing both your site and browser's caches and cookies. After that, perform a hard refresh. Instructions for a hard refresh can be found here: https://filecamp.com/support/problem-solving/hard-refresh/. This action may resolve the issue.
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 encourage you to open 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 you need further assistance, please contact us in the WPML support forum.
Problem: The client needed to add two domains for a single language in a WPML multi-site setup, which is not supported by default in WPML.
Solution: We informed the client that adding multiple domains for a single language is not possible within WPML's interface. However, we provided two alternative solutions: 1. Point the DNS of the additional domain to the existing language domain so that it redirects there. 2. Add a custom language for the other domain and duplicate all the content for that language. For more details, we recommended checking our official documentation:
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, 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 the WPML support forum.
Problem:
Client is experiencing issues with WPML automatic translation where the content appears translated in the translation view, but upon publishing, the translation does not display on the homepage, except for the translated page title.
Solution:
First, we recommend taking a full backup of your website and database. It's best to perform the following steps on a staging or development site to avoid compromising your live website:
- Upgrade WordPress to the latest version.
- Deactivate all plugins except for WPML and switch to a default WordPress theme like Twenty Twenty-Four to determine if the issue is theme-related. You can check theme compatibility at https://wpml.org/theme/.
If the issue persists, please:
- Edit the page in the original language.
- Make a small change to the content.
- Save the changes to refresh the entry in the database for that page.
- Update the translation and check if the issue is resolved.
If these steps do not resolve your issue, or if the solution provided here is 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 our support forum here: WPML support forum.
Problem: The advanced editor does not load anymore. Solution: We recommend clearing your browser cache as outlined in our errata on the Advanced Translation Editor (ATE) freezing issue. You can find the instructions here: https://wpml.org/errata/advanced-translation-editor-ate-freezing-issue-on-certain-browsers/. If this does not resolve the issue, we suggest trying a different browser to see if that fixes the problem.
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 open a new support ticket in the WPML support forum.
Problem: The client needs to export text from a page created with Bricks Builder, translate it using a spreadsheet, and then import it back in.
Solution: 1. If you can export the Bricks Builder content using WP ALL Export into a CSV file, you can manually add the translated content to this file. 2. Import the main file into the other site first to ensure the default content appears there. 3. Add translations to the CSV file and configure parameters to link the default content with its translations. Refer to our guide for details: Preparing Import Files for WPML Export and Import. 4. Import the file with translations to the site and navigate to "WPML > Export and Import" to run the import process.
Creating a spreadsheet file for each post or page with sentences separated as in the translation editor is not feasible. Content in the spreadsheet is presented in one line per ID for efficiency and maintainability.
If this solution is not relevant to your case, because it might be outdated or not applicable, we recommend opening a new support ticket. We also 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 need further assistance, please contact us in the WPML support forum.
Problem: The client is experiencing an issue where WPML translation is stuck loading, displaying only grey boxes. Solution: We recommend clearing your browser cache and testing the issue with different browsers to see if the problem persists.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, 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 you need further assistance, please contact us on the WPML support forum.
Problem: The client needed assistance with installing and integrating WPML on their site and inquired about the possibility of the WPML support team doing it for them, as their own attempts led to errors and they had to deactivate everything. Solution: We informed the client that while we do not perform custom work, we are available to help resolve specific issues and errors. For custom integration, we advised the client to consult our list of recommended contractors at https://wpml.org/contractors/. Additionally, we suggested that the client refer to our Getting Started guides at https://wpml.org/documentation/getting-started-guide/ for guidance on installing and configuring WPML.
Please note that the solution provided might not be applicable to your situation due to being outdated or not relevant to your specific case. If this is the case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and ensuring 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 at our support forum.
Problem: The client is unable to continue translating their website as the backend is endlessly loading, even though the frontend is working fine. Solution: We recommend clearing the site caching, which includes both local and server caching. Additionally, try accessing the backend from a different browser to see if the issue persists. If these steps do not resolve the problem, we suggest checking our related known issues and verifying that you have the latest versions of themes and plugins installed. If the solution provided here is outdated or does not apply to your case, please do not hesitate to open a new support ticket in our support forum.
Problem: The client is unable to load the translation screen for pages/posts despite all server parameters being okay. Solution: We recommend clearing the site caching, which includes both local and server caching. Additionally, we suggest trying to access the translation screen from a different browser. If the issue persists, it may be due to an outdated solution or because it's not applicable to your specific case. In such instances, 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 in the WPML support forum.
Problem: The client is experiencing issues with the menu not being displayed in English, as well as the text of the slider images and widget images. Additionally, the footer and posts integrated through the service grid element are not displayed in English on the English pages.
Upon further inspection, we confirmed that: 1. The menu is correctly translated into the English version. 2. The footer also appears correctly in English, although it may require style adjustments.
We asked the client if they needed assistance with adjusting the footer style or if there were still issues with the menu display.
If the provided solution is not relevant due to being outdated or not applicable to your case, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
