Problem: The client, António, reported that after translating and synchronizing the navigation menu on their website from English to French, German, and Portuguese, only the original English menu was appearing. Despite following provided tutorials and videos, the issue persisted. Solution: We advised António to first ensure that all content linked by the menu items was translated. This involved checking the translation status via WPML -> Translation Dashboard and translating any content that was not yet available in the desired languages. Additionally, we suggested checking for custom links in the menu under Appearance -> Menus and ensuring these were correctly configured in WPML -> String Translation. If the 'Look for strings while pages are rendered' option was missing, we recommended switching to human support for more personalized assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Also, please 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, you can contact our support team directly at the WPML support forum.
Problem: If you click on English, a popup template with an Elementor Pro loop grid widget appears. In the second and third columns on desktop, the custom CSS for the loop items is missing, although the items are translated. The popup items look correct in English but appear strange in other languages, with the editor showing white but visible in the Structure Panel. Solution: We have developed a small plugin to address this issue temporarily. Please back up your website first. Then, download and install the plugin from this link. After installation, make a minor change to the original page and ensure it is 100% translated. This should resolve the problem temporarily. Our development team is aware of the issue and is working on a more permanent solution.
If this solution does not apply to your case, or if it seems outdated, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client reported a critical issue with WPML Advanced Translation Editor (ATE) on a live WooCommerce + WPML multilingual store. When sending a product for automatic translation using ATE, the translation process crashed and created fatal errors, specifically an 'InvalidArgumentException'. Despite several actions such as clearing WPML cache, switching to Classic Translation Editor, and deactivating conflicting plugins, the issue persisted. Solution: We performed several troubleshooting actions under WPML → Support → Troubleshooting. After these adjustments, we tested translations on the client's site with successful results in both Arabic and Persian using ATE. We asked the client to verify if the issue was resolved on their end and to check if the translations were performed correctly.
If you're experiencing similar issues, we recommend trying the following steps: 1. Navigate to WPML → Support → Troubleshooting and run the necessary troubleshooting actions. 2. Ensure that your Automatic Translation account ID is correctly updated and matches the records. 3. Test the translation with a few products to confirm functionality.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: How to translate a string that is in a PHP snippet. Solution: If you're experiencing this issue, we recommend wrapping the text in a WordPress gettext function so that WPML can detect it when scanning the code. Here's a step-by-step guide:
After updating the snippet, navigate to WPML → Theme and plugins localization, scan the relevant source if available, then go to WPML → String Translation and search for the text to add its translation. For more details, visit our developer documentation: https://wpml.org/documentation/support/how-to-use-gettext/
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client set up a title bar image for each page using Avada layout section and defined the title and image location in Avada page options. After translating the first page, the title bar image did not appear on the translated page. Solution: 1. Navigate to WPML -> Settings and scroll to the Custom Field Translation section. 2. Search for fields starting with pyre_ or fusion_ (Avada's prefixes for Page Options). 3. For title bar background images and retina images, set them to Copy if the same image is desired across languages, or Translate if different images are needed per language. 4. Set heading and subheading text fields to Translate. 5. Click Save at the bottom of the page.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're trying to fix technical SEO issues like improper URLs and need these changes to propagate to different language versions of your site, you might encounter issues where changes do not always apply. This could be due to issues in the Media Translation add-on, specifically causing double slashes (//) in media links. Solution: First, ensure you have a backup of your site. Then, if you're comfortable with code changes, you can manually edit the file at
Save the changes. However, this is a temporary workaround. We have released WPML 4.9.3, which includes a permanent fix for this issue. You can download the new version from https://wpml.org/account/downloads/. After updating, you can remove the manual code edit.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing difficulties with duplicated pages and wants to eliminate all languages except the main language (de-at) from their WPML setup. They have also inquired about a cleanup plugin for removing languages. Solution: We recommend the following steps to effectively delete a language and clean up your site: 1. Delete or trash translated posts/pages/products for the language you no longer need. 2. Remove menus, widgets, and templates assigned to that language. 3. Remove String Translation entries that are specific to that language. 4. Clear all caches (plugin, server, CDN) after these changes. 5. Resave permalinks from Settings > Permalinks. For SEO considerations, since you are removing the language, consult with your SEO agency about redirecting links to avoid losing traffic.
If this solution does not fully address your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue with the WPML Translation Dashboard where the 'Words to translate' spinner never resolves, and the browser DevTools shows a 500 Internal Server Error for the endpoint '/wp-json/wpml/v1/get-words-to-translate-for-items'. Other related WPML REST endpoints function correctly. This problem persists despite extensive troubleshooting, including disabling plugins, switching themes, and disabling security measures. Solution: We have addressed a similar issue in a recent support forum post. We recommend checking the solution provided there to resolve the REST API 500 error. Please visit the following link for detailed instructions: WPML support forum post.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, please 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, you can also contact us directly through the WPML support forum.
