Problem: You are trying to translate buttons in Elementor on your site using WPML, but the translation does not work. Solution: First, use the browser's Inspect tool to check the HTML element of the button to confirm it is an Elementor widget from the theme Valiance and that it isn't registered for translation. Then, follow these steps: 1. Go to Registering Custom Elementor Widgets for Translation and How to Register Page Builder Widgets for Translation for guidance on creating an XML configuration. 2. Navigate to WPML > Settings > Custom XML Configuration tab. 3. Copy the following XML code and add it to your site:
This solution might be 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client is trying to synchronize products across different languages on their WooCommerce site using Judge.me, but faces issues because Judge.me does not detect products in different languages due to incompatibility with WPML. Solution: We recommend that the Judge.me developers join the WPML Go Global Program to achieve compatibility. They can reach out to us through https://wpml.org/documentation/support/go-global-program/. Additionally, Judge.me has opened a feature request for WooCommerce multilanguage compatibility with WPML, which can be viewed here: https://feedback.judge.me/suggestions/115563/woocommerce-add-multilanguage-compatibility-with-wpml.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problema: Utilizzi il plugin WooCommerce Quote or Enquiry Contact Form 7 sul tuo sito WordPress e hai tradotto i moduli in Contact Form 7. Tuttavia, le traduzioni non vengono visualizzate correttamente e i moduli mostrano solo il contenuto in lingua originale (italiano), nonostante la configurazione. Soluzione: Il problema non riguarda il modulo stesso, ma il modo in cui il plugin inietta il codice nella pagina shop o in altre pagine. Se utilizzi lo stesso shortcode da solo, questo viene tradotto senza problemi. Probabilmente è necessario aggiungere un hook di WPML per identificare la lingua e mostrare il modulo corretto. Ti consigliamo di contattare l'autore del plugin per discutere questa integrazione. Se l'autore ha problemi, può partecipare al nostro programma Go Global e noi lo aiuteremo a rendere il plugin compatibile.
Se questa soluzione non risolve il tuo problema o sembra non essere più attuale, ti invitiamo a verificare i problemi noti, a controllare la versione della correzione permanente e a confermare che hai installato le ultime versioni dei temi e dei plugin. Se il problema persiste, ti consigliamo di aprire un nuovo ticket di supporto.
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 working on a site under development and trying to translate sections of your Elementor pages using WPML. Some parts of your Elementor pages are not translating, and you are unable to get the XML file for translation. Solution: We recommend the following steps to resolve the issue: 1. Add the following XML in WPML >> Settings > Custom XML Configuration section:
2. Make a small change in the default language page title to reload the translation and press the Update button. 3. Remove the change made in step 2 and press the Update button again. 4. Click on the secondary language icon to open up the page in Advanced Translation Editor and add the translation. If the issue persists, you might need to implement a workaround for a known issue with Elementor tabs not displaying translated templates correctly. Follow the steps outlined in this errata: https://wpml.org/errata/exclusive-addons-elementor-tabs-widget-does-not-display-the-elementor-template-translation/ If these solutions do not resolve your issue or if they seem 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where product options added by 'Bopo - WooCommerce Product Bundle Builder Premium' plugin, from the Arabic single product page do not appear on the checkout page when using WooCommerce Multilingual & Multicurrency with the WPML plugin.
Solution: We have identified that the plugin 'Bopo - WooCommerce Product Bundle Builder Premium' and the theme 'Enzy' are not compatible with WPML. Unfortunately, none of the plugins from VillaTheme are currently compatible with WPML. We recommend contacting the plugin and theme authors and asking them to join the WPML’s Go Global program to ensure compatibility. You can find more information about this program and encourage your theme/plugin provider to participate here: Go Global program.
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 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, you can contact us directly through our support forum.
Problem: You are trying to translate your site using WPML, but on some pages, most of the content is missing from the translator. This issue occurs because you are using an unofficially compatible theme that adds custom page builder widgets, which are not registered with WPML. Solution: To resolve this, you have two main options: 1. Request the theme author to join our GoGlobal program so we can collaborate to make the theme fully compatible with WPML. 2. Manually add support for the custom widgets by following the instructions in our documentation on how to register page builder widgets for translation. Additionally, if you are using Elementor in your default language, ensure to use the same page builder for the second language to maintain consistency in the translation process. You can find more details on using different translation editors for different pages here.
If these solutions do not apply because they are outdated or not suitable for your case, 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: The client is trying to translate the footer of their website using WPML, but the translated footer does not appear. Solution: We noticed that the footer is generated from the 'wdt_footers' post type and assigned using the footer meta box inside the page edit screen. It seems there might be a compatibility issue between the 'Neytri' theme and WPML, as this theme is not listed in our verified compatibility theme list (verified compatibility theme list). We recommend contacting the theme author to inquire about compatibility fixes or to encourage them to join our Go Global Program (Go Global Program). Alternatively, you could:
Create the footer using the Elementor Pro plugin from the Templates >> Theme builder page and display it on any or all pages using conditions. More details can be found here: Elementor header-footer builder.
Open the default language page in Edit mode, disable the WPML Translation Editor from the Languages metabox, open the secondary language page in the default WP Editor, select the correct language Footer from the Footer metabox, and press the Update button. More details can be found here: using different translation editors.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, we highly recommend checking related known issues (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 an issue where the font changes from Noto Serif Georgian to Roboto when switching from the Georgian version to the English version of their multilingual website. Solution: 1. Navigate to WPML -> String Translation and use the search field to look for the font name strings. Ensure all instances, especially those under 'admin_texts' in the domain name, are translated. 2. If the font issue persists, go to the bottom of the String Translation page and click on 'Translate texts in admin screens'. Search for the font string in the admin texts, add it for translation, and translate it. 3. If these steps do not resolve the issue, it might be necessary to manually set the font via CSS for different elements like
p
,
h
tags, etc., to ensure it displays correctly in both languages. 4. Since the theme used is not officially compatible with WPML, consider contacting the theme author for further assistance or to make the theme compatible through our GoGlobal program: https://wpml.org/documentation/support/go-global-program/
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 for further assistance.
Problem: The client's plugin developer is encountering an issue with the
flush_rewrite_rules()
function when deactivating a plugin, which conflicts with WPML, leading to a 500 error. The developer has temporarily commented out this function in the plugin's deactivation hook to avoid the error. Solution: We recommend that the plugin developer joins the WPML Go Global Program to collaborate directly with our team for a compatible solution. Details about the program can be found here.
If this solution is outdated or does not apply to your case, 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 issues persist, we highly recommend opening a new support ticket here.
Problem: If you're trying to translate a global element created with Bricks Builder and are encountering issues where the translation does not appear correctly on the frontend.
Solution: We recommend following these steps: 1. Apply the fix from the WPML errata page for Bricks Builder issues. You can find it here: Bricks translated content not showing on frontend. 2. Edit the home page in the default language using Bricks Builder and make necessary text changes. 3. Save your changes and exit to WordPress. 4. Update the translations in the Advanced Translation Editor (ATE), ensuring all text is present and translated. 5. If some elements still don't display correctly, go to WPML -> String Translation. Search for the strings that are not showing correctly, correct their language if necessary, and translate them. For guidance on changing the language of a string, visit: How to change the source language of strings. 6. Note that if you are using plugins like 'Max Addons for Bricks' which are not compatible with WPML, you might need to manually translate some elements using the WP Editor. For more information on using different translation editors, see: Using different translation editors for different pages.
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.
