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: 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: 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: The client is experiencing translation errors on their website and has issues with the WPML plugin not showing updates due to incorrect site registration. Solution: 1. Visit your WPML account at https://wpml.org/account/sites/ 2. Remove any existing registrations for the site. 3. Unregister the site from the WPML plugin by navigating to your-domain.com/wp-admin/plugin-install.php?tab=commercial and clicking 'Unregister this site'. 4. Re-register the site by clicking 'Register this site', which will redirect you to your WPML account to complete the registration. 5. Copy the new site key provided and enter it back on your site's WPML plugin page.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to configure the WPML plugin for automatic translations with the Leksa theme but is facing issues as many elements do not automatically appear in the WPML translation editor. The client needs help setting up the wpml-config.xml file correctly. Solution: We recommended using the Multilingual Tools add-on to generate the XML configuration. Detailed guidance on setting up the XML file can be found in our documentation: https://wpml.org/documentation/support/language-configuration-files/ We also advised the client to ensure that a full backup of the site is created before making any changes. After updating all plugins and themes to their latest versions, we registered the homepage elements following the steps described in our guide: https://wpml.org/documentation/support/multilingual-tools/ The client was then instructed to go to WPML -> Translation Management, select the homepage, and send it for translation to check if all elements now appear.
If this solution does not resolve your issue, or if it seems 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where the WooCommerce lateral menu in the My Account section is not visible in the Spanish version of your site, this summary might help. Solution: We recommend following these steps to resolve the visibility issue: 1. Edit the English page using the UX Builder. 2. Access the post settings. 3. Change the template from 'Default Template' to 'WooCommerce - My Account' template. 4. Save the changes and exit the settings. After these adjustments, refresh the Spanish My Account page to check if the sidebar is now visible.
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: You are trying to link already translated pages to multiple languages on your site using the 'connect with translations' link, but you can only connect one other language instead of the two additional languages. Solution: Here are the steps to connect each translated page to your default language page: A) Connect "French page" as French (FR) translation of "Dutch page": - Edit your "French page". - Expand the Language section and set the language of your page to French. - Switch to WordPress Editor, and in the popup that appears, leave the selection at This Post. Click Apply. - Click on Connect with translations. A popup will appear. Search for the "Dutch page" and click Ok. - Another dialog will appear. Uncheck the box if you do not want to set the current page as the default language. B) Connect "English page" as English (EN) translation of "Dutch page": - Repeat the steps as above, setting the language to English. C) Connect "German page" as German (DE) translation of "Dutch page": - Repeat the steps as above, setting the language to German. After following these steps, your pages (French, English, German) will be linked as translations of the Dutch page.
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.
Problem: You are trying to translate the placeholder text in Contact Form 7 using WPML, but the placeholder does not appear on the translation page as expected. Solution: If you're experiencing this issue, we recommend checking the syntax used for your placeholders. Contact Form 7 requires double quotes for placeholder text. For example, if your form code looks like this:
[text* yourname placeholder 'YOUR NAME*']
You should update it to:
[text* yourname placeholder "YOUR NAME*"]
After updating, retranslate the form. This should resolve the issue and the translated placeholder should appear correctly on the frontend.
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 was experiencing persistent loading and sporadic 404 errors on translated pages of their website after using WPML. The issues included pages not displaying after translation and random 404 errors when switching languages. Solution: We recommended the following steps to troubleshoot and resolve the issues: 1. Ensure all pages are correctly translated by making a minor edit in the original language, saving it, and then updating the translation. 2. Check and flush cache settings, as stale cache data might lead to pages not loading correctly. 3. Deactivate and reactivate plugins to identify any that might be causing conflicts, particularly focusing on the 'Razorpay for WooCommerce' and 'Categories Images' plugins, which were found to be problematic. 4. Switch the language URL format settings in WPML to see if this affects the 404 errors. 5. Increase the WordPress memory limit to ensure sufficient resources are available for operations. 6. If issues persist, especially with specific plugins like 'WooCommerce PayPal Payments', deactivate them to check if the problem resolves.
If these steps do not resolve the issues, or if the solution seems 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. For further assistance, 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
