Problem: The client is experiencing an issue where some media files are only visible in one language and not in others within the WordPress media library. Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML-> Support ->Troubleshooting. 2. Click the following buttons: -
Clear Cache in WPML
-
Set Language information
-
Fix element types collation
-
Remove ghost entries from the translation tables
-
Assign translation status to duplicated content
-
Fix post type assignment for translations
3. After completing these steps, run the media duplication settings again.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
Problem: The client is experiencing an issue where an Elementor popup is not displaying the correct layout in the English translation, despite following forum instructions and setting the custom fields for
Next, we re-translated the page "Teenused" using the Advanced Translation Editor. We searched for the popup post ID, added the translation popup ID to the translation content, and saved the changes. This resolved the layout issue for the popup.
Additionally, we provided a screen recording of the steps taken to fix a similar issue with a button in the header on another page. The steps included editing the template or page, making a small change, saving it, updating the translation, searching for the popup ID in the Advanced Translation Editor, translating the ID, and completing the translation.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us.
Problem: The client is unable to see the translated product category on their website. Solution: We recommend checking if the menu itself is translated. To do this, navigate to Appearance-> Menus in the WordPress dashboard and review the menu translation. For detailed guidance on translating menus, please refer to our documentation: Translating Menus.
Problem: The client needs to assign Automatic Translation Credits to their website and is unsure how to do it from their account. Solution: We recommend following the steps in our documentation to assign the Automatic Translation Credits from your account to your site. Here is a step-by-step guide: Visit the documentation on How to Assign Automatic Translation Credits to Your Sites: https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/
If this solution doesn't look relevant, please feel free to open a new support ticket in our forum: WPML Support Forum
Problem: The client was unable to see the translated categories in the Arabic version of their website, even though they had translated them and published products within those categories. Solution: We accessed the client's website and changed the category order to "Name" in Appearance -> Widgets -> Shop Sidebar. This action made the categories appear correctly in the filter. We advised the client to check if the categories now work as expected. If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
Problem: The client has enabled the option to fallback to the original product data if a translation is not available. However, when selecting languages such as Swedish (sv) or German (de), product variation swatches are missing, even though other data displays correctly.
Solution: 1. We explained that the issue occurs because the attributes have already been translated into Swedish and German, and therefore, they do not display the fallback translation as expected. 2. We suggested that if the client has translated the attributes, they should also translate the product into the secondary languages. Alternatively, the client can duplicate the product. We provided documentation on how to duplicate content: https://wpml.org/documentation/translating-your-contents/displaying-untranslated-content-on-pages-in-secondary-languages/#duplicating-content 3. We clarified that the translation preference 'Translatable - use translation if available or fallback to default language' means that if a translation for an attribute is available, it will not display the fallback in the original language.
If this solution does not seem relevant to your situation, please open a new support ticket with us here.
Problem: The client was unable to see the currency switcher dropdown on a newly created test product page. Solution: We found that the issue was due to the absence of the "Currency Switcher" widget in the custom Divi layout for that specific product. To resolve this, we recommend adding the currency switcher Widget to the layout. Here's how you can do it: 1. Edit the product page with Divi. 2. Add the "Currency Switcher" widget to the layout using the "Sidebar" module. 3. Save the changes and check the product page to ensure the currency switcher appears. If you're experiencing this issue, please follow these steps to add the widget to your custom product layout. If this solution doesn't seem relevant to your problem, please open a new support ticket with us, and we'll be happy to assist you further.
Problem: The client is experiencing issues with the appearance of WPML language flags in the menu, which do not look aesthetically pleasing due to the menu titles. Solution: We recommend adding custom CSS to improve the appearance of the language flags. Here are the steps to follow: 1. Navigate to your site's backend. 2. Go to Appearance > Customizer > Additional CSS area. 3. Add the following CSS code:
4. Save the changes. This should adjust the width of the dropdown menu to look better. However, if you're looking to have the flags under a world icon with a transparent background, this would require custom coding. Custom work is beyond our support policy, so you may need to hire a developer or consider reaching out to a WPML contractor.
Problem: The client wants to change their translated URL to be the same as the main language URL. Solution: 1. Navigate to WordPress Dashboard > WPML > Settings > Translated documents options. 2. Select the option "Copy from original language if translation language uses encoded URLs". 3. Click Save to apply the settings. 4. Go to Dashboard > Pages and open the edit screen of the original page. 5. In the sidebar options under the "Languages" section, make a minor edit to the page, such as adding an extra space. 6. Save the changes to trigger an update. 7. Once a circular arrow appears beside the second language's links, indicating an update is needed, edit the translation again. 8. Save the translation after ensuring it is 100% translated. For additional guidance, refer to our documentation on translating page slugs.
Problem: The client's privacy policy page content is not displaying for translations in the Advanced Translation Editor (ATE). The page was created using WP Bakery Page Builder. Solution: We recommend deleting the current text module on the privacy policy page, adding a new one, and then saving the page. This action should make the strings appear correctly in the translation editor. If this solution does not seem relevant to your issue, please open a new support ticket with us for further assistance.
Problem: If you're experiencing issues with the 'Flexible PDF Coupons' plugin by WpDesk on a multilingual site, where the German PDF template is sent for orders placed from secondary language versions of the site instead of the respective English or French templates, even though you have assigned specific templates to each language version of the product.
Solution: We recommend contacting the plugin author to request a compatibility update with WPML. We provide resources for developers to make their plugins compatible:
Additionally, encourage the plugin author to join our Go Global program, where they can work with our compatibility team to ensure their plugin works seamlessly with WPML.
Problem: The client is experiencing an issue where the translation tool throws an error related to HTML markers, particularly when there is too much bold text in one translation box. This error prevents saving the translation and causes the tool to revert to the original automatically translated text, resulting in the loss of the client's manual edits.
Solution: 1. We recommend opening the page in the Editor and ensuring that any HTML markers added to the content are correctly formatted. 2. Make a small change and then update the Translation. 3. In the Translation Editor, format the HTML correctly by following our guide on HTML markers. 4. If you're having trouble identifying which marker needs to be fixed, please share the link to the page where you're having the issue, and we will check and guide you accordingly.
Problem: The client is struggling to translate their site using WPML, especially when working with Elementor. They encounter issues where only titles and SEO elements are translated, but not the content. A database error indicating a missing table
icl_string_packages
is found in the debug log. Solution: We recommend performing a WPML reset as the table
icl_string_packages
is missing, which is likely causing the translation issues. Here are the steps to follow: 1. Backup the database and website. 2. Follow the instructions in our documentation to reset WPML: WPML Reset Documentation. 3. Reinstall WPML and recheck the issue.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is experiencing an issue where WPBakery icon box titles are not displaying in German after translation, only in English when switching to the German version of the site. Solution: We added custom XML configuration to the WPML settings to ensure that the icon box titles are translatable. Here are the steps we recommend: 1. Navigate to WPML-> Settings-> Custom XML Configuration tab. 2. Add the following code:
3. Update the page in the default language. 4. Update its translation using the WPML translation editor. You can find the translation editor at WPML translation editor.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us for further assistance.
Problem: If you're trying to remove credits from your website. Solution: To remove credits: 1) Go to your WPML Account. 2) Find the site and click Add/remove credits. 3) Click Remove credits and enter the number of credits. 4) Click Remove credits to complete.
If you need to remove credits from a site that shares credits with other sites: 1) On your site, go to WPML → Translation Management and click the Tools tab. 2) Click Settings and expand the setting to Transfer credits to WPML.org. 3) Enter the number of credits you want to transfer. These credits are available immediately in your WPML account to use on other sites.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
