The client is trying to translate links in the content of an Elementor page, specifically for images, but the links go to the original untranslated pages instead of the expected translated pages.
Solution:
If you're experiencing this issue, we recommend you follow these steps: 1) Navigate to WPML>>Settings>>Custom XML Configuration. 2) Add the WPML language configuration for the Elementor Widgets. 3) Save the changes. 4) Update the Homepage. Additionally, please refer to our documentation for more detailed guidance:
Make sure to translate the Image URLs from the WPML Translation Editor and ensure the links work as expected.
Please note that 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.
Problem: The client reported that two of their multilingual URLs set up using WPML on their WordPress site suddenly became non-functional, displaying an 'SSL handshake failed Error code 525'. However, one URL remained operational. Despite the SSL certificates passing tests on ssllabs.com, the issue persisted. Solution: We analyzed the situation and determined that the issue was not related to WPML. The 'SSL handshake failed' error indicates that Cloudflare could not establish a secure connection with the origin server. We recommended: 1. Verifying that the origin server has a valid SSL certificate installed and is correctly configured to serve HTTPS traffic. 2. Ensuring that the SSL/TLS settings in Cloudflare match the setup on the server (e.g., Full vs. Full (Strict)). 3. Contacting Cloudflare support for further assistance to identify where the connection is failing.
If this solution does not resolve your issue or seems 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. Additionally, if further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing a black screen with a 'get Adobe Flash Player' message when switching to English after changing the default language on your website, it might be due to a folder conflict. Solution: We recommend checking your website's directory for a folder named 'en'. This folder could be causing the issue by interfering with the language switch functionality. You should either delete this folder or rename it. For instance, renaming it to 'en-old' might resolve the issue.
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 problem persists, please open a new support ticket.
Problem: The client reported two issues: Firstly, the 'Add to basket' button on the checkout pages for individual products in Traditional Chinese displayed in English, and the relevant string was not found in WPML String Translation. Secondly, after changing the default language back to Traditional Chinese, the language settings on some backend pages were reversed. Solution: For the first issue, we advised the client to enable the 'Include translations' option within WPML->String Translation to locate and translate the string correctly. A screencast was provided to assist in this process: https://www.loom.com/share/b6b76dc6f22b49e6a4b73ab13b7e58c6. For the second issue, we identified it as a separate problem that needed escalation, and we created a new ticket for further investigation.
If this solution does not resolve your issue or seems outdated, we 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.
Problem: Using LearnPress LMS, the search feature returns all the courses, not by language. Solution: If you're experiencing this issue, make sure you have active the addon WPML Add-on for LearnPress. It is necessary to enable search functionality specific to each language.
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.
Problem: The client was unable to update to WPML version 4.7 and faced issues with their glossary disappearing after attempting updates and key changes in a staging environment. The glossary was not stored locally but on WPML's servers, and the client was concerned about the loss of translations and glossary entries. Solution: We advised the client to ensure they were not using the beta channel for updates and to switch to the production channel to check for updates. If necessary, the update could be manually downloaded from the WPML.org account. For the glossary issue, we confirmed that glossary entries and automatic translations are stored under an ATE (Advanced Translation Editor) account on WPML's servers, not linked to the WPML registration key. We recommended ensuring that both staging and production environments are connected to the same ATE account to avoid issues like missing glossary entries or unsynced translations. If discrepancies continue, we suggested re-registering the WPML key without affecting existing translations or glossaries, as these are managed separately through the ATE account. For detailed steps on managing glossary entries, please refer to this documentation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum.
Problem: You are working on a site under development and trying to translate a logo image using Beaver Builder. Solution: First, we removed the language file named
1
admin_texts_theme_mods_bb-theme-child-es_ES
from the directory
1
public_html/wp-content/languages/wpml
. Please check if the issue is resolved on your staging site. If the logo still appears incorrect, follow these steps: 1. Go to WP > Appearance > Customize > Header > Header logo and select the correct Spanish image. 2. Translate the logo using the string translation available at WPML String Translation.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with translating products on their WordPress site using WPML. The translations are stuck at 'in progress', and products are not being translated as expected. Solution: We have confirmed that all systems, including the Advanced Translation Editor (ATE), are now functioning correctly. There may be a short delay as the system processes a backlog of jobs. We recommend trying the translation process again and checking if the issue persists.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and confirm that you have installed the latest versions of themes and plugins. If the problem continues, we highly recommend opening a new support ticket for further assistance at our support forum.
Problem: You are trying to translate a page or post using the Advanced Translation Editor (ATE) in WPML, but the editor doesn't load and keeps spinning. Solution: We recommend testing the ATE again to see if it works now. The issue should have been resolved. 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 at WPML support forum for further assistance.
Problem: You are trying to translate AltTexts for images included through the WP-Carousel plugin on your site, but when images are included through a carousel, there is no option to translate the AltTexts - they are always shown in English. Solution: We recommend modifying the WP-Carousel plugin's code to include WPML's filters for translating attachments. This change will allow you to translate the original media directly in the media library, without needing to translate the carousel or its meta-fields.
Please note that this solution might be outdated or not applicable to your specific case. If this solution does not resolve your issue, 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 at WPML support forum.
Problem: The client was experiencing issues with the WPML Media Translation plugin where images uploaded while editing in different languages were not being associated correctly with those languages. Solution: We clarified that when using the WPML plugin, any images uploaded while editing a page are automatically associated with the language currently being used. For instance, if you're editing the Spanish version of a page, any image uploaded during this session will initially be linked to Spanish. You can then translate this image into other languages as needed. Similarly, images uploaded while editing the English version will be associated with English. This feature helps WPML determine the original language of media files.
If you're experiencing this issue, we recommend checking that you are uploading images in the correct language context. If the problem persists, please replicate the issue on our staging site here: WPML Media Staging Site.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at 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 continues, do not hesitate to open a new support ticket for further assistance here.
Problem: You are trying to use the translator to translate a page to Dutch, but you cannot access the page to edit the translation. Solution: We recommend that you attempt to access the translation page again as the issue have been resolved. 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 do not hesitate to open a new support ticket. You can contact us directly for further assistance at WPML support forum.
Problem: The client was experiencing an issue where the translation editor would scroll to a random spot after saving, instead of moving to the next string. This problem was accompanied by the appearance of additional strings from Yoast SEO. Solution: The client managed to resolve the issue by turning off Custom Fields Translation for Yoast SEO and enabling the display of system fields in Custom Term Meta Translation. Despite previous attempts, this solution was effective only after the correct settings were applied.
If you're experiencing similar issues, we recommend trying the steps the client took. However, if this solution does not apply to your case, or if it seems outdated, please check the related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and consider opening a new support ticket for personalized assistance. For further help, you can contact us directly at WPML support forum.
Problem: The client is experiencing issues where manually translated posts from English to Dutch using WPML revert back to English in certain parts such as paragraphs, buttons, and affiliate links. This occurs even after translations have been set and not modified for a period. Solution: 1. Ensure that you are using a consistent method of translation. Mixing translation methods (ATE/WPML editor and manual/WordPress editor) can lead to content being overwritten when the default language page is updated. Choose one method and stick to it. For more details on using different translation editors, visit Using Different Translation Editors for Different Pages. 2. Update the WPML plugin and all related add-ons to the latest version to ensure all bug fixes and improvements are applied. Instructions for updating can be found at How to Install WPML. 3. If issues persist after updating and ensuring consistent translation methods, consider setting up a staging site to replicate the issue, which can help in further troubleshooting.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, 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. For further assistance, please contact our support at WPML Support Forum.
Problem: The client is experiencing issues where they are initially taken to the Translation Queue instead of directly to the translation editor when starting a new translation for products. Additionally, they encounter errors such as 'WPML couldn't translate this page' and 'The website is under heavy load' when attempting to translate certain templates. Solution: We have identified that the issue occurs specifically with a certain template and not with other pages or posts. The problem persists even when exporting and importing this template into a different custom post type and attempting to translate it. Since the root cause is unclear, we have escalated the matter to our second-tier support for further investigation. We will provide updates as soon as we have more information.
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, 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 open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
