Problem: The client is experiencing issues with product tag pages on their WordPress site, which are either redirecting to images or showing 404 error pages after the site went live. The URLs for these tags, when translated to Swedish, are not retaining the desired slug but revert to the default 'produktetikett'. The client is also concerned about the SEO impact of these errors and is considering changing the URL structure or setting tags to 'No follow'.
Solution: 1. To address the issue of the tag slug reverting to its default Swedish value, we recommend updating the slug from WPML → Settings. After updating, verify the accuracy in WPML → String Translation. 2. For updating the product category slugs to maintain 'product-category' for the Swedish version and change it for the English version, you can adjust these settings in Settings → Permalinks, and then translate them in WPML → Settings.
If this solution does not resolve 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem:
A client was experiencing an issue with WooCommerce where the Japanese product page displayed ¥85,000, but the English page displayed ¥75,100 instead of dollars. This issue occurred when the WooPayment plugin was enabled and resolved by disabling it. Also, the new development site does not experience this issue.
Solution:
We explained that in a development environment, new plugins are frequently added and settings are changed, so enabling/disabling plugins can sometimes clear the cache. Therefore, we recommend clearing the cache when there are major changes, when adding, removing, enabling/disabling new plugins, or when changing the theme.
This solution may be outdated or not apply to your case. In that case, please check for related known issues , check the version of the permanent fix, and make sure you have the latest version of your theme and plugins installed. If the issue persists, please open a new support ticket on the WPML support forum .
Problem: The client experienced a crash in their webshop after attempting to install WPML for the first time. The crash was accompanied by multiple PHP Deprecated warnings and a PHP Fatal error related to an empty string for the language code. Additionally, after resolving the initial crash, WPML did not translate the root page of the site. Solution: To address the crash and PHP errors: 1. We recommended resetting WPML completely. This involves going to WPML → Support, clicking the Troubleshooting link, and in the Reset section, selecting the 'I am about to reset all translation and language data' checkbox, then clicking the 'Reset and deactivate WPML' button. 2. If the problem persists, we suggested sharing wp-admin and FTP access to a staging site for further investigation. To resolve the issue with the untranslated page: 1. We advised checking if the Divi Templates were translated. This can be done by going to WPML > Translation Management > Dashboard, creating a job for each template, sending them to automatic translation or assigning the jobs to yourself, and then accessing them at WPML > Translations to translate them with the WPML Translation Editor.
If these solutions do not resolve your issues or seem 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.
Problem: If you're experiencing an internal server error when trying to translate pages using WPML, particularly with pages containing images without metadata, this might be due to a known issue. Solution: We recommend waiting for the upcoming WPML 4.8.1 update, which addresses this issue. You can check the progress and details of this known issue on our errata page: WPML 4.8 Fatal Error When Translating Pages Containing Images Without Metadata.
If this solution does not apply to your case, or if it seems outdated, please 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.
Problem: The client was experiencing performance issues on their site's archive pages, particularly with high load times and frequent errors. The WPML_Element_Translation->maybe_populate_cache() function was being called excessively, resulting in around 1,800 SELECT queries per request, significantly affecting site performance. Solution: We identified that the issue was related to the Adjust ID setting in WPML, which was trying to fetch translated IDs for menu items not set in other languages. To resolve this, we recommended the following steps: 1. Disable the Adjust ID option. 2. Navigate to WPML > String translation > Admin Texts Translation. 3. Locate the default language theme option for the main menu at [theme_mods_motors][nav_menu_locations]primary with ID 207. 4. Add this option for translation and assign the translated menu ID for other languages, such as French ID 253. After applying these changes, the site's load time improved significantly, with pages loading in about 2.5 seconds even with cache disabled. For further details on optimizing SQL queries, you can visit https://wpml.org/faq/how-to-optimize-mysql-queries/.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is unable to view credits from their account or the website's Translation Tools page. Solution: We recommend the following steps to resolve the issue: 1. Navigate to Plugins -> Add New -> Commercial in your website. 2. Unregister WPML by clicking the unregister link. 3. Visit https://wpml.org/account/sites/ and delete the existing site key. 4. Create a new site key. 5. Return to Plugins -> Add New -> Commercial in your website and click the register link to use the new site key. If the issue persists: - Take a full backup of your site and database. - Deactivate all plugins except WPML and String Translation. - Switch to a standard theme like 2024 or 2021. - Repeat the registration steps. For PAYG users, manage your invoices and usage reports at Automatic Translation Invoices and share credits across sites at Automatic Translation Subscription for Multiple Sites. Ensure you are using the latest versions of WPML, String Translation, and related addons for improved functionality. We also recommend clearing site cache, WPML cache (from WPML -> Support -> Troubleshooting), and browser cache.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, please open a new support ticket. 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, visit our support forum at WPML Support Forum.
Problem: You are trying to use the WPML advanced translation editor and XLIF for translating content that includes a repeatable metafield group, which is JSON encoded in the database. However, only the title text appears as a translatable item in the advanced translation editor, while the classic editor displays all translatable fields. Solution: First, ensure that the repeatable field group is correctly registered and appears in your database as a serialized array. You can use the example from the CMB2 documentation to set up testable fields: example-functions.php. Next, navigate to WPML > Settings > Custom Fields Translation and set the field group (e.g., "yourprefix_group_demo") to 'Translate'. This action should make all fields provided with values available for translation when you send the content to the WPML Advanced Translation Editor (ATE). If the fields still do not appear, consider sending the page or post for translation via WPML > Translation Management to create a new translation job with the current settings. If issues persist, we recommend setting up a sandbox environment to demonstrate the functionality with CMB2 fields, which can serve as a reference.
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 continues, please open a new support ticket.
Problem: If you're trying to translate specific parts on a product page and can't locate the strings, you might be unsure where to find them. Solution: We recommend searching for these strings within WPML -> Strings Translation. If you do not find the strings there, it's possible they are not registered in the String Translation interface. In this case, please refer to our guide on finding unregistered strings: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
If this solution does not apply because it might be outdated or not relevant 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 you still need help, please open a new support ticket at WPML support forum.
Problem: You have set up a WooCommerce store in two languages using WPML and noticed that while Arabic products are visible on the website, they are not showing in the WooCommerce Mobile App. Solution: We have identified that products and categories in secondary languages are not visible on the WooCommerce Mobile App. This behavior is expected as product translation is only available and visible within the WordPress dashboard. Unfortunately, this issue cannot be resolved from our side. However, you can still view translated products by accessing the WordPress admin through the mobile app. For more details, please refer to our erratum: https://wpml.org/errata/woocommerce-mobile-app-translated-products-and-categories-not-displayed/
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing a 404 error on your WooCommerce category page due to a compatibility issue with Rank Math, it might be related to the 'Remove parent slugs' option or incorrect slug translations for different languages. Solution: 1. Check if the 'Remove parent slugs' option in Rank Math is causing the issue. A temporary fix can be found in our errata: https://wpml.org/errata/rank-math-seo-remove-parent-slugs-option-causes-category-slug-translation-error-404/ 2. If the issue persists, you may need to adjust the slug translations: - Navigate to WPML > Settings > Slug translations and ensure it is enabled. - Go to WPML > Taxonomy Translation > Product Categories and check the slug translations for each language. - Ensure that the slug translations are either blank or a copy of the original WordPress settings: 'product-category'. 3. If you have modified the Rank Math plugin files as a workaround, ensure to update the slug translations accordingly. You might need to edit the original pages and update the translations in the Advanced Translation Editor.
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 at WPML support forum.
Problem: The client is translating the 'About Us' page from English to Arabic using WPML and Elementor. A specific paragraph is missing in the WPML translation editor, although it appears in the English version created with Elementor. Solution: 1. Ensure that the English page is not currently in a translation job by checking WPML -> Translation Management -> Jobs. If it is, complete the job and update the English page again. 2. If using Elementor widgets that are not officially compatible with WPML, this might cause issues with visibility in the translation editor. It's recommended to switch to the WordPress editor to avoid WPML overwriting manual changes made in Elementor. 3. For pages where manual translation fixes are applied, consider using different translation editors for different pages as outlined here: Using Different Translation Editors for Different Pages.
If this solution does not resolve your issue or seems outdated, 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. We highly recommend opening a new support ticket if the problem persists. You can do so here: Contact WPML Support.
Problem: The client has 46,000 prepaid credits assigned to their site, which are visible under Sites Using Prepaid Credits in their WPML.org account. However, within WordPress (WPML → Translation Management → Automatic Translation), the system does not recognize these credits and prompts the client to purchase more. Despite attempts to deregister/re-register the site, reassign credits, and clear caches, the issue persists. Solution: We first asked the client to navigate to WPML > Support > Troubleshooting and share the Advanced Translation Editor ID to identify any issues with multiple activations that might have affected the credit assignment. After receiving the necessary information, we corrected the issue on our server. We recommend the client to check their WordPress dashboard now to confirm that the credits are now properly recognized.
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. Should the problem persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where your contact page, initially translated into Dutch, keeps reverting to English despite multiple translations. Additionally, the URL does not correctly reflect the Dutch translation. Solution: We recommend adding a specific constant to your wp-config.php file to prevent automatic updates from overwriting your translations. Please insert the following line of code into your wp-config.php file:
If this solution does not apply to your situation, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client is creating a bookable virtual product with selectable resources and custom people enabled, where each person counts as a reservation. With WCML active, after booking a resource for fewer people than the resource's total availability, the resource becomes unavailable for that day if more than one resource is selected. Solution: We recommend updating WPML, Strings Translation, and WooCommerce Multilingual & Multicurrency to the latest versions as this resolved the issue in a similar case. Please check if the updates solve the problem on your site. If the issue persists, we suggest recording the steps you took using a screencast service like Komodo and sharing it with us for further investigation.
Please note that this solution might be irrelevant if it's 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 continues, please open a new support ticket for personalized assistance.
Problem: You are trying to install the WPML plugin using the OTGS Installer, but it is not working across multiple websites. Solution: If you're experiencing this issue, we recommend following these steps to resolve it: 1) Visit https://wpml.org/account/websites/ 2) If the site URL is already registered, delete it from the list. 3) Re-enter the site URL to create a new site key. 4) Click "Show key" and copy it. 5) Go to Plugins > Install > Commercial (tab) on your WordPress dashboard and enter the key to re-register WPML. If WPML is still registered there, de-register it first.
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 you still need help, please open a new support ticket at 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
