Início›Suporte›Tag do Tópico: Elementor Custom Widgets
Elementor Custom Widgets
All issues in which we had to help clients with Elementor Custom Widgets either because they wanted to create one, or (more likely) when related to themes that have Elementor Custom Widgets integrated. Add whether you helped, sent to docs or escalated.
Problem: The client needed to translate the cart title 'il mio carello' which is set in an Elementor widget added by the jet-blocks plugin.
Solution: We recommended the following steps: 1. Navigate to WPML -> Settings -> Custom XML Configuration and save the following code to register the widget for translation:
2. Go to Templates and search for the template 'Orte Header Webshop'. 3. Edit it using Elementor, make a minor modification to the Italian template (add an empty space, for example, and save it) so WPML recognizes that there's an update available for the translation. 4. Edit the translation of the template, and the item 'il mio carello' should now be available for translation.
After performing these steps, 'il mio carello' should appear as 'my cart' in the English version of the site.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket for further assistance.
Problem: The client is unable to translate a contact form created with the Metform plugin and Elementor widgets on their multilingual site. Solution: A. Translate the form content: 1. Navigate to WPML > Settings > Post Types Translation and set the post type "metform-form" to Translatable. 2. Go to WPML > Settings > Custom XML Configuration and add the following code to translate the form fields:
3. Visit Metform > Forms and translate the form titled "New Form # 1693676945". B. Translate the widget form on the contact page: 1. Follow step 2 above to add a custom XML code to translate the form ID:
2. Switch to the English language in Metform to retrieve the form ID from the URL, which is 2710. 3. Add the following PHP code to the file functions.php in the theme folder to make the number translatable in the Advanced Translation Editor:
4. Update the contact page and its translation. 5. In the Advanced Translation Editor, search for the form ID and translate it. Now, the form should appear translated on the frontend. Refer to the documentation for further details:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client was unable to translate custom posts, custom post taxonomies, and templates using Crocoblock and Elementor Pro. Additionally, internal links were not working correctly in other languages, and custom taxonomies created with Crocoblock Jetengine were not appearing in the taxonomies translation section. Solution: We advised the client to ensure that custom taxonomies and post types are configured to be translatable in WPML settings. We provided documentation to guide them through this process:
The client managed to resolve the issue by updating the saved versions of their pages, which helped create the correct links. They also realized that WPML does not support Elementor's recent feature to add links into any container under its additional options. The client worked around this by adding the link into the text within the container and manually updated the menu translations to correct the links.
If you're experiencing similar issues, we recommend following the steps outlined above. However, please note that the solution might be irrelevant due to being outdated or not applicable to your case. If these steps do not resolve your issue, we highly recommend checking 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: The client reported that while using WPML for automatic translation with automatic publishing, only the page titles were being translated and not the full content created with Elementor. Solution: We identified two main issues and provided solutions for each: 1. There was a TypeError in the theme's code. We modified the code in /wp-content/themes/powerlegal/elements/element-templates.php at line 1312 from:
This change fixed the post loop issue. We recommend reporting this issue to the theme's author as without their intervention, the client might need to reapply these fixes after each theme update. 2. To ensure the translation of Elementor widgets, we added custom XML configuration in "WPML > Settings > Custom XML Configuration" as follows:
Please note that 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 the issue persists, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate a site from French to English and encounters an issue where English text appears in the French part of the translation editor. This text seems to be coming from an Elementor module or plugin. The client identified the strings in the string translator but was unable to change their language settings individually due to them being part of a 'packet'. Solution: We explained that the issue arises because the widget used by the client defaults to English strings in its code, which can only be changed by editing each string within the widget. This is a design issue with the widget, and the plugin author would need to include language files for different default languages. We also informed the client that our team is actively working on compatibility with many Elementor addons and provided a list of compatible addons. We mentioned that Royal Addons is not yet fully compatible and that we have reached out to the author for a resolution. If you're experiencing a similar issue, we recommend checking if the Elementor addon you are using is compatible with WPML by visiting our compatibility page: https://wpml.org/compatibility/2021/08/the-best-elementor-addons-for-multilingual-sites/.
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 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 with us.
Problem: The client needed assistance with two issues: translating the filter labels 'All', 'Room', and 'Rooms' on the homepage and archive pages, and changing the Cyrillic translations to Latin for the Serbian language on the Cart and Checkout pages in WooCommerce.
Solution: 1) To translate 'All', 'Room', and 'Rooms': - Go to WPML > String Translation. - For 'All', type 'All' in the search box, select "Exact match", and click the "Search" button. Translate the string found under the "augustine-core" domain by clicking the "+" icon under the language flags. - For 'Room' and 'Rooms', type '%s Room' in the search box and press the "Search" button. Translate the strings under the 'augustine-core' text domain using the same method.
2) To translate WooCommerce strings on the Cart and Checkout pages to Latin for the Serbian language: - Go to WPML > Theme and Plugins Localization. - Select the "WooCommerce" plugin and scan it for strings. - Once the scan is complete, navigate to WPML > String Translation. - Input the text you wish to translate in the search box, using English as the source language. For example, type "Product" instead of "Производ". - If the string is under the 'woocommerce' text domain, add a translation for the Serbian language by clicking on the "+" icon below the Serbian flag.
Please note that the solution provided might be outdated or not applicable to your case. If the steps above do not resolve your issue, 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. If you still need assistance, please open a new support ticket.
Problème : Le client ne parvient pas à traduire certains éléments de templates Elementor, tels que les boutons "Fiche" et "Jouer" sur la page d'accueil, en utilisant le thème Zine. La traduction via WPML ne montre pas tous les éléments du template et la duplication du template pour chaque langue conduit à une erreur 404 dans Elementor. Solution : Nous avons informé le client que le thème Zine utilise des widgets qui ne sont pas compatibles avec WPML par défaut. Pour résoudre ce problème, nous avons recommandé d'enregistrer les widgets personnalisés pour qu'ils soient détectables par WPML en suivant ces étapes :
De plus, nous avons suggéré au client de télécharger et d'installer le plugin Multilingual Tools depuis GitHub pour aider à rendre tous les widgets visibles pour la traduction : https://github.com/OnTheGoSystems/multilingual-tools.
Si cette solution ne s'applique pas ou si elle est obsolète, ou si le problème persiste, nous recommandons vivement de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent et de s'assurer que les dernières versions des thèmes et plugins sont installées. Si nécessaire, le client doit ouvrir un nouveau ticket d'assistance pour obtenir de l'aide supplémentaire.
Problem: The client was unable to save certain strings in the string translation. Solution: We recommended that the client first install the multilingual-tools plugin from https://github.com/OnTheGoSystems/multilingual-tools. After installation, we advised following the steps outlined in our documentation for registering custom Elementor widgets for translation. The client can find the guide here: Getting Started and Using WPML Config Generator for Elementor. We also offered to check the XML generated by the WPML Config Generator if the problem persisted.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, 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. If necessary, please open a new support ticket in the WPML support forum.
Problem: The client was unable to translate the Contact Form 7 widget on their Contact page, which was created by the Elementor widget "reycore-cf7" from the Rey theme. Additionally, the client could not find where to translate the tab names on their product pages, such as "détails du produit", "livraison", and "conseils de lavage". Solution: We instructed the client to register the "reycore-cf7" widget for translation by adding the following code to WPML > Settings > Custom XML Configuration:
If the solution provided does not apply to your case, or if it seems outdated, we recommend checking the 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 was unable to find where to translate text on a WooCommerce shop page, which was added through the Title widget from the Themerex addons. Solution: We suggested that since Themerex addons are not included in our list of compatible plugins, the widget might not support translation, which could be why the content is not available for translation. We recommended following the steps provided in a previous support ticket that addressed a similar issue:
If you're experiencing this issue, we recommend trying the steps mentioned in the provided link. However, please note that the solution might be irrelevant due to being outdated or not applicable to your case. If the problem persists, 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 do not hesitate to open a new support ticket with us.
