Problem: The client was experiencing issues with automatically translating entire pages and specific custom-coded content on their website using WPML, similar to their previous experience with the gtranslate plugin. They were particularly concerned about the main page and category pages not being translated in English and German, despite being okay in Polish.
Solution: We advised the client to ensure they had used the Automatic Translation feature correctly, as it should automatically translate all content that WPML can detect. For content that WPML does not automatically translate, such as custom-coded sections or taxonomies, the client needs to: 1. Ensure that any custom code is properly registered with WPML. For guidance on this, see Translating the Theme You Created. 2. Set themselves up as a translation manager or translator with access to all language pairs under WPML->Translation Management-> Translators. More details can be found here: Setting Up Translators. 3. For translating taxonomies automatically, follow the steps outlined in Translating Post Categories and Custom Taxonomies.
If these steps do not resolve the issue or if the solution 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the header button on your site using WPML. The translation works with subpages but not with posts. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Copy the footer template ID. 2. Go to WPML-> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the ID. 5. Select the string. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the ID into the translated templates IDs. For more detailed instructions, please check our guide on translating texts on the admin texts screen.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where YouTube videos only display the cover photo on product pages when WPML Multilingual CMS is activated, even in the original language, and you're using the Woodmart theme, we can help.
Solution: 1. Navigate to WPML-> Settings-> Custom Fields Translation. 2. Click on "Show System Fields". 3. Search for and set the following fields to "Copy": -
woodmart_wc_video_gallery
-
_product_image_gallery
4. Click "Save". 5. Edit the product in the default language, make a minor edit, and update it. 6. Update its translation. After these steps, the video should appear correctly in all languages.
If the issue persists even when WPML is deactivated, it might not be related to translation. In this case, try creating a new test product in the default language with WPML activated and add the video. Check if the video displays correctly on the front end.
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 need help translating footer elements, specifically the footer menu links, using WPML. Solution: If you're experiencing difficulties translating footer elements, we recommend following these steps: 1. Go to WPML → String Translation. 2. Enable "Look for strings while pages are rendered". 3. Navigate to the page where untranslated strings are displayed. 4. Return to WPML → String Translation and verify if the given string has been registered. 5. Translate the string. For more detailed guidance, visit our documentation on How to translate footers and headers.
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 needs to remove specific content only from the secondary languages (English and German) on a multilingual site using WPML and the Enfold theme. Solution: We suggest two methods to address this issue: 1. Use CSS to hide the content in the secondary languages. Navigate to Appearance > Customizer > Custom CSS and add the following code:
2. Manually remove the content from the secondary languages. Go to your site's backend, access "Pages", switch the language to English, and use the Avia builder to edit and remove the unwanted content. Repeat the process for German.
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 experiencing slow site performance due to frequent calls to /wp-json/wpml/tm/v1/ate/jobs/retry and /wp-json/wpml/tm/v1/ate/jobs/sync, which trigger multiple admin-ajax.php calls on every admin page load. Solution: We recommend the following steps to improve performance: 1. Check the ATE Error logs by navigating to WPML->Support->ATE Error logs and review the top 5 logs. 2. Deactivate the plugin 'User Import Export for WooCommerce Add-on' when it is not in use. 3. In WPML > Settings, adjust the 'display as translated' settings for post types, taxonomies, and custom fields to 'Translatable only show translated items'. For example: - Pages: Set to 'Translatable only show translated items' - Downloads Products (product): Set to 'Translatable only show translated items' 4. Disable the WPML Media Translation add-on if you are not using a different image per language. 5. Run WPML troubleshooting actions via WPML->Support->Troubleshooting, specifically: - Set language information - Fix Terms Count - Remove Ghost Entries - Cleanup and Optimize string tables
These steps helped reduce the dashboard loading time from 2.04s to 1.63s with WPML activated.
If these steps do not resolve your issue or if the solution 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.
Problem: The client was experiencing a white screen when trying to configure translations in a WordPress site using the Divi theme, even after disabling other plugins and switching themes. The issue persisted despite adding debug code to wp-config.php. A DOMException error related to cross-origin stylesheet access was noted in the browser console.
Solution: We recommended enabling WordPress debugging to capture any PHP errors that might be causing the white screen. This involved editing the wp-config.php file to include:
We also suggested inspecting the page using the browser's developer tools to check for JavaScript errors in the console and reviewing the ATE error logs in the WPML support section. Additionally, we explored the possibility of a cross-domain issue if different domains were used per language and recommended testing the directory format in WPML settings.
Ultimately, the problem was resolved by creating a new admin user and accessing the site with the Chrome browser, suggesting a potential corruption in the old user profile in the database.
If this solution does not apply or is outdated, we recommend checking related known issues at https://wpml.org/known-issues/, verifying you have the latest versions of themes and plugins, and if needed, open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate menu links in a nested menu created with Elementor, but encounter issues where translations are lost when the header is modified, and automatic scans do not detect these links for translation. Solution: First, ensure that links are visible in our translation editor. By default, links might be hidden. You can make them visible by using the search bar at the top left of the editor and searching for "http". This action should allow you to see all links from that page and translate them accordingly. For more details, visit Translating Links with Advanced Translation Editor. If this does not resolve your issue, we need more information about how the menu was created and translated. Please provide additional details or share screenshots or a short video using loom.com to help us better understand your configuration.
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 at WPML support forum for further assistance.
Problem: You are trying to access the Translation Management and got the migration banner. Solution: If you're experiencing this issue, we recommend you follow these steps: 1) Ensure you back up your database. 2) Navigate to WPML → Support and click on the Troubleshooting link. 3) On the WPML Troubleshooting page, click the Force-enable WPML’s Advanced Translation Editor button.
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: You are developing a site and need to list the language on a mobile device. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Provide your debug information to help us understand your configurations better. You can find this in WPML > Support > click on the Debug information link. For more details, visit http://wpml.org/faq/provide-debug-information-faster-support/. 2. After ensuring you have a full backup of your site, proceed with these steps: - Navigate to WPML > Languages > Menu language switcher. - Add a new language switcher to the mobile menu. - Go to WPML > Support > Troubleshooting page, and click on the Clear the Cache in WPML button.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. For further assistance, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are experiencing issues with page warnings stating 'page does not exist' when clicking on the translation Edit and View links, and you are also trying to update the styling to the site tagline. Solution: We recommend making a slight change to the page, saving this change, and then resending the page for translation through WPML → Translation Management. After this, attempt to complete the translation of the page. Additionally, ensure that the language pairs are correctly configured for your account, which you can do by following this guide on configuring language pairs.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing issues with untranslated strings on the Cart and Checkout pages of your website in Latvian, while Russian translations are complete. Solution: We have reviewed your Cart page and identified some strings that were not translated. To resolve this, please follow these steps: 1. Navigate to the WPML > String Translation section of your website. 2. Search for the strings that are not appearing in Latvian. 3. Ensure that you have translated all necessary strings into Latvian. We recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists or if this solution does not apply to your case because it might be outdated, please open a new support ticket.
Problem: The client reported an issue where variable products randomly displayed as 'out of stock and unavailable' after WPML was uninstalled. The client suspected that WPML might have been uninstalled incorrectly, potentially leaving duplicate variations in the database. Solution: We recommended following a specific guide to ensure that WPML was uninstalled correctly, which can be found here: WPML Reset Guide. If the problem persists after following the reset process, it is unlikely that WPML is the cause. We suggested further investigation by allowing us access to the site to potentially escalate the issue to our second-tier supporters. We also emphasized the importance of security and privacy, advising the client to back up site files and database before providing access, and preferably sharing access to a staging site if available.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we 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. If further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing issues with the flag icon not appearing in the main menu after switching to 'auto translate everything' mode in WPML, despite not clicking the 'Sync Menu' button or manually creating translations. Additionally, you encountered a PHP Fatal error indicating an exhausted memory limit. Solution: First, increase the WordPress memory limit by adding the following lines to your wp-config.php file:
Add these lines above the '/* That's all, stop editing! Happy blogging. */' line. This adjustment should help resolve the memory issue and allow for smoother operation of WPML functionalities.
Next, ensure your site key is correctly registered to use automatic updates. If updates are not working, generate a new site key by deleting the current site URL from your WPML account at https://wpml.org/account/sites and re-adding it. This action will provide a new site key. Then, unregister and re-register WPML on your site with the new key by navigating to Plugins -> Add New -> Commercial tab and following the prompts to update or enter the new site key.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your specific case, 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client was unable to find and translate a specific string in the header of their website using WPML. Solution: 1. To make the custom Marquee Elementor element compatible with the WPML Translation Editor, we added the following XML configuration in WPML >> Settings > Custom XML Configuration section:
After this, we made a small change in the default language header template and translated the header in the secondary language. This made the marquee element content available for translation. 2. For translating the 'Donation' text, we followed these steps: - Navigated to WPML >> String Translation page. - Clicked on the 'Translate texts in the admin screen' link at the bottom of the page. - Searched for the string and enabled its translation. - Assigned the correct source language and added the translation of that string. - Cleared the cache to reflect the updated translation. For further details, you can refer to the following documentation links:
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive