Problem: The client was experiencing an issue where the Testimonials element in Elementor displayed both English and Portuguese languages on the front page instead of showing the correct language translations for each site version. Solution: We investigated the issue by confirming the WPML settings and testing the site in a minimal environment. We identified that the issue was with the 'Testimonial Card' Elementor element provided by the Grand Tour Theme Elements for Elementor plugin. We resolved the issue by modifying the code in the plugin. Specifically, we added
'suppress_filters' => false
to the query arguments in the file at wp-content/plugins/grandtour-elementor/templates/testimonial-card/index.php. We also recommended that the client contact the theme author to incorporate this modification for future updates and consider joining the WPML Go Global Program (https://wpml.org/documentation/theme-compatibility/go-global-program/).
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 (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 where the translated pages in Mongolian are not following the layout set in the default language on your site. This affects all Mongolian pages, with the layout and template settings not syncing correctly, resulting in a broken homepage in Mongolian compared to the default language version. Solution: We recommend deactivating the Elementor plugin and then reactivating it. This action has resolved similar issues in the past and might fix the layout synchronization problem for the Mongolian translations on your site.
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. Additionally, please feel free to open a new support ticket with us for further assistance at WPML support forum.
Problem: You are using Thrive Editor with WPML, which is not fully compatible, causing issues with the display of translated pages. You are considering either editing each translated page individually or switching to a compatible editor like Elementor and re-translating the content. Solution: If you choose to switch to a new editor like Elementor and re-save the original pages, WPML will treat this as creating new content due to the different shortcodes and content blocks used by different editors. Consequently, WPML will attempt to re-translate the content, which may incur additional translation costs. If you decide to manually fix the design issues on the translated pages using Thrive Editor, any future updates to the translation might revert these pages to their previous broken state.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise checking the related 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.
Problem: You are trying to have your site, originally made in English, translated into Italian using WPML. While the pages and products are translated to Italian as intended, when you change the store's default language to Italian, the store shows 0 products. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WordPress Dashboard > WPML > Languages and change the default language to Italian. 2. Go to WordPress Dashboard > Settings > Permalinks. 3. Click the "Save" button to flush the permalinks cache. After these steps, both languages should work correctly, and the product page should display the products.
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: If you're experiencing issues with automatic translations being stuck on 'waiting for translator' and the wait time for the next translator keeps increasing, this might be due to the translation jobs being queued. Solution: We recommend the following steps to resolve this issue: 1. Navigate to WPML > Settings and switch the Translation Mode to 'Translate What You Choose'. 2. Go to WPML > Translation Management, access the Jobs tab, and cancel all jobs listed under 'Need Translation'. 3. Return to WPML > Settings and change the Translation Mode back to 'Translate Everything Automatically'. This should allow your pages and products to be translated automatically. Note that products in Draft mode will need to be sent for translation manually from the Translation Management board.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related 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.
Problem: You are experiencing issues with a custom checkbox field in WooCommerce products not saving its state across translations. You need the checkbox to be consistent for all languages and editable only for the original product. Solution: 1) Navigate to WPML-> Settings-> Custom Fields Translation section, search for your fields, and set them to Copy. 2) After setting the fields to copy, update the products in the default language and check if the field values are copied correctly. 3) We also recommend providing your Debug information to help us better understand your site configuration. You can find a detailed explanation on how to provide this information here.
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. If the problem persists, we highly recommend opening a new support ticket here.
Problem: The client is managing a WordPress website using WP Event Manager with WPML, with Bulgarian as the main language and English as the secondary language. They encounter issues when accessing event pages in English directly, often resulting in a 404 error. However, accessing the same event in Bulgarian and then switching to English using the language switcher loads the page correctly. Solution: We recommend testing the website in a staging environment with only WPML and WP Event Manager plugins active to isolate the issue. This approach helps determine if the problem is specific to the plugin interaction or another underlying issue. Monitoring the site for any specific triggers causing the 404 error can also be beneficial.
If this solution does not resolve the 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. If problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You have set up your site using TheGem Theme and configured category-based templates for single posts. Although you have set TheGem Templates to be non-translatable in WPML settings to use a single global template ID across all languages, this setup works only for the default English version. Translated posts in other languages do not adopt the correct layout despite having the correct global template ID assigned in the backend. Solution: To resolve this issue, it is necessary to create separate TheGem templates for each language, as WPML loads translations for posts, pages, or any other custom post types (CPT) in this manner. You should keep the translation of the Templates CPT active and translate it as described here: Translating Templates Documentation. Enforcing a single template ID across all language versions of posts in the same category is not supported by default and might require custom coding, which is beyond our standard support scope.
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: If you're editing text in the original language on your site and then attempt to correct the text in another language using WPML's Advanced Translation Editor, you might find that the translation in the second language disappears. This issue occurs when the system detects changes in a segment, requiring you to retranslate and review it. Solution: When you add new text in the primary language and save changes, ensure you use the "Complete Translation" button in the Advanced Translation Editor. This process should help in retaining the translations based on the translation memory. If the translation still does not appear, it might be necessary to manually re-enter and retranslate the affected segments. For more details on how translation memory works and can assist in this process, you can read here: https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, we recommend opening a new support ticket. Additionally, we highly advise 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 migrated their website from production to a staging environment and then back to production, resulting in the loss of all WPML credits for the second website. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your wpml.org account and go to the Sites page. 2. Delete the site key for https://ranescreation.com by pressing the little trash icon, which will return the assigned credits to your WPML.org account as mentioned in this documentation: Why credits may be missing and how to fix it. 3. Log in to https://ranescreation.com, navigate to Plugins >> Add new Plugin > Commercial tab and click the ‘Unregister WPML from this site’ link if it exists. 4. Click the ‘Register WPML’ link. 5. Click the ‘Get a key for this site’ link. 6. It will generate the Key for your site and you can also assign the credits using that popup. 7. Copy the key and paste it back to the input box and press the Register button.
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. If needed, please open a new support ticket at WPML support forum.
Problem:
The header is not showing the button and translated sites in the menu on the .co.uk site. The issue resolves when the Litespeed cache plugin is turned off. Solution:
Litespeed support added "elementor" to JS excludes. Relevant Documentation:
Problem: You are trying to add Serbian Cyrillic to your website, which already has Serbian Latin and English.
Solution: To add Serbian Cyrillic to your website using WPML, follow these steps: 1. Visit the WPML → Languages section in your admin panel. 2. Click on 'Edit Languages' under Site Languages. 3. Scroll down and select 'Add Language'. 4. Fill in the details for Serbian Cyrillic. 5. In the 'Language Mapping' column, choose the appropriate option for Serbian (Cyrillic or Latin). 6. Save your changes. For more detailed guidance, check the following documentation:
If you encounter difficulties or this solution does not apply to your 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. If the issue persists, please open a new support ticket.
Problem: The client is trying to synchronize credits with their website for automatic translation using WPML, but the credits and the website are not linking correctly, and the URL appears incorrect. Solution: We recommend following these steps to resolve the issue: 1. Log in to your WPML.org account and navigate to the Sites page: https://wpml.org/account/sites/ 2. Delete the site key for https://www.carbonaltdelete.eu by clicking the trash icon, which will return the assigned credits to your WPML.org account. More details can be found here: https://wpml.org/documentation/automatic-translation/why-credits-may-be-missing-and-how-to-fix-it/#removing-a-sites-registration-from-wpml-org 3. Log in to https://www.carbonaltdelete.eu, go to Plugins >> Add new > Commercial tab and click the ‘Unregister WPML from this site’ link if it exists. 4. Click the ‘Register WPML’ link. 5. Click the ‘Get a key for this site’ link. 6. It will generate a Key for your site and you can also assign the credits using that popup. 7. Copy the key and paste it back to the input box and press the Register button. If these steps do not resolve the issue, please add a debug report in the Debug Information box. You can find how to provide this information here: https://wpml.org/faq/provide-debug-information-faster-support/
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 you still need assistance, please open a new support ticket.
Problem: The client created two menus using Elementor for their website, one as a mega menu for desktop and another for tablet and mobile. While the menus displayed correctly in English, the tablet and mobile menu incorrectly showed the desktop menu style in Arabic. Solution: We advised the client to ensure that the Elementor header template was properly translated into Arabic. After verifying that the translation was not initially done, we sent the header template for translation via WPML > Translation Management. Once translated, the client was instructed to manually translate the AR menu by accessing https://colorfulrainbeauty.com/wp-admin/nav-menus.php?menu=109&lang=ar and adding Arabic text to the menu items. This resolved the issue, and the menus began displaying correctly in Arabic.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing a site crash when accessing Payments > Overview with WPML enabled, displaying the error: TypeError: m.enabled_payment_method_ids is undefined. Solution: 1) We recommend checking your server error logs to identify what might be causing the issue. 2) Increase your server resources to ensure that the site does not run out of the necessary capacity. 3) Temporarily disable any firewalls that might be blocking access to your site's admin or FTP, as this is necessary for us to investigate the issue.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please visit our support forum and 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
