Problem: The client translated the homepage into English and German using WPML, expecting the URLs to be nissei.nl/en and nissei.nl/de respectively. However, both URLs redirected to the original Dutch URL, nissei.nl, as did the URL nissei.nl/en/machines/, which redirected to nissei.nl/machines/. Solution: We identified that the redirection issue was caused by settings in the Yoast SEO plugin. We recommended checking and adjusting the redirection settings within the Yoast plugin to resolve the problem. Additionally, we advised updating WPML and its add-ons to their latest versions to ensure compatibility and functionality, especially if further investigation into the issue was required. We also emphasized the importance of making a full site backup before making any changes.
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 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where the translation of a page using WPML is stuck at 97% completion and cannot be saved. This problem arises because the HTML markers in the translation do not match those in the original text, which is essential for maintaining the page's HTML integrity. Solution: To resolve this issue, ensure that the HTML markers are identically set in both the original and translated text. This involves selecting the text with the mouse and clicking on the marker to set it correctly. There should be no spaces between markers and no markers should be missing. This requirement helps prevent accidental HTML styling breaks, link omissions, or design issues. For more detailed guidance, refer to the WPML documentation on safe HTML editing: Safe HTML Editing. If adjusting the markers does not resolve the issue, please open a support ticket.
If these solutions do not apply or if the problem persists, we recommend opening a new support ticket. It's also advisable to check 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. For further assistance, please visit our support forum: WPML Support Forum.
Problem: You are building a new website and trying to move all products in two languages from one site to another. You followed the WPML export and import documentation, but the products only imported in Spanish, and the English versions did not import. Solution: If you're experiencing this issue, we recommend that you first go to WPML > Export & Import and set up the import dialog before running the import. After running the import, you should again visit WPML > Export & Import and run the dialog to connect the imports.
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 at WPML support forum.
Problem: The client is experiencing an issue where the translated Header and Footer do not appear when switching to the German version of the site, despite the translations being completed. Solution: We recommend adding the following code to your theme's functions.php file to ensure that the translated Header and Footer are displayed correctly. Please ensure to back up your site before proceeding:
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 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was unable to find where to translate the string "Meer weten" in the header, even with the string translation tool. Solution: We recommended the following steps: 1. Navigate to WPML > String Translation. 2. At the bottom of the page, expand the section "Not seeing the strings you are looking for" and click on "Admin Texts Translation". 3. Search for "meer weten" and click on "Add to string translation". 4. Return to WPML > String Translation, where the string should now appear. 5. You may need to change the source language of the string. For guidance on this, visit how to change the source language of strings. 6. Translate the string and verify the changes on the front end.
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 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 open a new support ticket.
Problem: The client was experiencing issues with translated pages, posts, and portfolios losing styles and not displaying like the original. Additionally, some content was not appearing in the translation editor, and there were problems with untranslated strings in Elementor widgets and custom fields. Solution: 1. We registered the necessary Elementor widgets for translation by adding custom XML configuration in WPML->Settings->Custom XML tab. Here is the code used:
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 the problem persists, please open a new support ticket.
Problem: You are trying to translate pages and posts, but the translations remain stuck at 'in progress' and do not change to complete. Additionally, your newly translated site redirects to an HTTP ERROR 500. Solution: We have identified that the issue might be related to your child theme. We recommend switching from your child theme to the default parent Astra theme, as this change has resolved the issue. It's also advisable to review any custom code in your child theme with your developer. Furthermore, ensure that you update the Astra theme to the latest version.
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. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're trying to translate the 'buy now' button on the WooCommerce checkout page and it's not translating, even after trying solutions from other forum topics. Solution: We recommend taking a backup of your site and then applying the workaround provided in our errata page. You can find the necessary steps and details here: WooCommerce Multilingual Cart Page Strings Not Translated When Using Blocks. Additionally, for more information on WooCommerce shortcodes, please visit: WooCommerce Shortcodes Documentation.
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. If you still need assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: You are trying to translate strings from English to Spanish on your website, but some strings are not being translated when switching from English to a non-English language. Solution: We found that the Elementor template was not translated. We recommend translating the Elementor template to resolve this issue. If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at the WPML support forum.
Problem: The client is experiencing issues with the MegaMenu on a multilingual WordPress site using WPML. In the German version, the Products menu item shows categories but no products, and clicking on a category leads to an incorrect URL. Solution: 1. We reviewed the MegaMenu code and found that the product categories were added but were pointing to the wrong URLs. We updated the code to be language-aware by adding a WPML language parameter and setting the language before querying products. 2. We also checked the slug translation issue and found that WordPress does not allow duplicate slugs across languages, which is not controlled by WPML. 3. We recommended setting up a staging site and activating a default WordPress theme to confirm if the issue is caused by the custom menu walker in the theme. If the problem persists, it may require custom development.
Please note that this solution might be 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 at WPML support forum.
Problem: You are trying to translate the English elements of an Elementor checkout page using WPML string translation, but despite translating them in the string translation section, no changes are visible on the page. Solution: 1. First, ensure that you have followed the steps mentioned in this forum post. 2. If the issue persists, go to WPML-> String Translation, search for the problematic strings, delete their translations, and then re-translate them.
If these steps do not resolve your issue, or if the solution seems outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: You are trying to improve your website's SEO and noticed that images with the class 'wpml-ls-flag' on your homepage do not have an alt attribute. Solution:
Problem: You are experiencing 404 errors on translated pages of your website. The error temporarily resolves after saving the permalink settings twice but reoccurs after navigating other pages. Solution: We recommend the following steps to permanently resolve the 404 error on translated pages: 1. Navigate to WPML -> Settings -> Post Types Translation. 2. Expand the option 'Set different slugs in different languages for Trainingen'. 3. Translate the slug to your desired languages, for example, DE (ausbildung) and EN (training). This should resolve the issue of 404 errors on translated pages.
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. If the issue persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You have a page with text content that is not displaying correctly on the translation page. Instead of showing the actual content, it displays odd strings like "core/list" and "core/paragraph". Solution: We recommend canceling the current translation job for the affected language at WPML > Translation Management > Jobs. Then, edit the original page and save it. After saving, open the translation editor again. This should allow you to see the original content, in this case, French, ready for translation.
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 at WPML support forum for further assistance.
Problem: The client reported issues with their multilingual WooCommerce site using WPML. Specifically, the Romanian shop page was displaying products but not the sidebar, the English shop page was showing the sidebar but not the products, and a Romanian product page was not displaying the sale price, only the regular price. Solution: We recommended the client to first clear any caches on their site, as caching can often cause display issues like these. Next, we advised checking the WPML language configuration settings to ensure that the shop pages are correctly linked and translated in both languages. For the issue with the product pricing, we suggested verifying the WooCommerce multilingual settings for currency and price synchronization between languages. If these steps do not resolve the issues, or if the solution becomes 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. If problems persist, please open a new support ticket at WPML support forum 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
